| |||||||||||||
|
| |||||||||||||
The Xaraya Web Application FrameworkThe Xaraya Web Application FrameworkPosted Apr 14, 2005 21:54 UTC (Thu) by AJWM (guest, #15888)In reply to: The Xaraya Web Application Framework by yodermk Parent article: The Xaraya Web Application Framework
No specific experience with Xaraya here, but having had some experience with PHP, Java, and even (shudder) ASP, I'm inclined to think that you're just seeing an inherent property of general purpose, customizable, heavily OOP-based CMSes, unless they've got powerful servers to run on.
Too many levels of indirection going on with all that general purpose customizability. ;-)
That said, I'm willing to give Xaraya a try. I've been thinking about overhauling one of my web sites for a while now.
(Log in to post comments)
The Xaraya Web Application Framework Posted Apr 15, 2005 14:24 UTC (Fri) by yodermk (subscriber, #3803) [Link] The problem with PHP was, last I checked, it had to parse all the PHP code for every web request, including the object initialization, and run it all anew. I'm not sure that objects persist well across HTTP requests (but maybe they do now, PHP has probably improved).
Still, I believe that compiled languages are inherently better for this kind of thing. We write all kinds of desktop apps in C/C++, why shouldn't web apps that have hundreds of simultaneous users?
The Xaraya Web Application Framework Posted Apr 21, 2005 10:00 UTC (Thu) by addw (guest, #1771) [Link] Use APC to cache your compiled PHP code ... makes things run much faster. http://pecl.php.net/package/APC
|
|
||||||||||||