I mainly wanted to bring it up because I see it as one of the main real benifits of PHP for web programming (at least as it is used): A programmer can use a database as a temp file system of sorts, without having to think about what it will take to get it used.
This then means that the sysadmin doesn't have to allow the PHP user to write files to the system: They just install a database, and let the PHP user use that instead.
The end result is easier to both use and administer: The PHP user can't access the filesystem (which means they don't have to be limited to what they can and can't do, and that it is impossible to perform a lot of trojan-executable attacks), so the admin doesn't have to worry about it, and the PHP user doesn't want to access the filesystem, so they never think about it.
In reply to Re^4: PHP over perl
by DStaal
in thread PHP over perl
by targetsmart
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |