Why is a Web site like Facebook so large that the PHP file is directly used as a path

Just like its login address, like this http://www.facebook.com/login.php . Usually most of the PHP site does not do some routing distribution, the actual address hidden it? Why doesn't Facebook do this, does it really call this file directly login.php ? Not so simple, what's the process behind it? Said the insider.

Reply content:

Just like its login address, like this http://www.facebook.com/login.php . Usually most of the PHP site does not do some routing distribution, the actual address hidden it? Why doesn't Facebook do this, does it really call this file directly login.php ? Not so simple, what's the process behind it? Said the insider.

1. Why must it be hidden?
2. Even if this is the case, then this must be the actual address?
3. Does this address have to be routed?
4. In fact, Facebook is now all deployed hiphop, it is not directly execute the PHP source code.

Easy to use on hiphop , if the unified entrance, once a file updated, it is necessary to import into the final output page of the file all compiled, this workload is very large, and, error prone! , and when it goes wrong, other features go wrong!

But independent, just with the login.php relevant files compiled can! and the sub-server is also more convenient ...

