Posted by David on 09/16/05 04:03
I found and interesting article, "Experiences of Using PHP in Large
Websites" (http://www.ukuug.org/events/linux2002/papers/html/php/) ,
which lists some issues with scaling PHP for larger projects. Worth
a read although it appears to be three years old.
The major issue I have had with PHP is a conflict in class names for
modules created by two project teams. We resolved this by prefixing
all class names with a module ID, ex. "ModuleName__<Class Name>"
The only mistake I can see with this article is a statement that you
can only have one php.ini per server.
Who is using PHP for larger projects and how do you handle the naming
issue?
[Back to original message]
|