Re: Function caching...

I have been following this thread for quite awhile, and I can no longer risk making a comment. Performance of a web - scripting language and an application server have *completely* different goals. The performance enhancements that Kristian is requesting can really be no benefit to anyone else but an application server. Any customization has to be judged if it can benefit everyone. In response to the 08/15 statement, I personally have been involved enterprise projects consisting over 100,000 lines of php source ( I wrote a great deal of this ), and the performance is through the roof. PHP is not designed for 08/15 counters, its designed for large scale web projects, with the ease of 08/15. Comparing PHP to simple guestbooks is over gratifying an application server. If you really want to design a good app server, you need a solid core, and this core needs to be optimized to the specific needs of being an App Server. Do you see the different goals that Zeev is trying to explain? You desire a multithreaded daemon, with a web module to utilize IPC between the web-server and the App-Server. This, of course, generates thousands of security concerns. We all know how secure first time revisions of new Unix daemons are. If you really like the language, then start a project, and use the Zend engine. You have to realize that sometimes there has to be 2 different projects because there are 2 different needs. This happens all the time with open source software. -Jason ----- Original Message ----- From: "Zeev Suraski" <zeev@zend.com> To: "Kristian Köhntopp" <kk@netuse.de> Cc: <php-dev@lists.php.net> Sent: Monday, December 11, 2000 8:52 AM Subject: Re: [PHP-DEV] Function caching... At 18:46 11/12/2000, Kristian Köhntopp wrote: >Zeev Suraski wrote: > > I *know* what PHP was designed to do. What he's describing is *NOT* what > > it was designed to do, and it's not a big surprise that he has to change it > > completely, all the way to the bones, in order to do it. > >These changes cannot be that big. If PHP or the Zend core of PHP >were to be used as, say, the procedural language in MySQL, it would >be a long running process running multiple interpreter threads, just >like in an application server. > >Well, we will see, how much really needs changes... I didn't say that it will require big changes. Much like the fact that I can plug the Zend Engine in MySQL doesn't mean that users should start serving their Web pages off stored procedures, the fact you can create a Zend engine based application server doesn't mean that PHP should *become* that application server. It doesn't matter if you'll have to change 2 lines, 500 lines or 10K lines... What matters is what you end up with. Zeev -- Zeev Suraski <zeev@zend.com> CTO, Zend Technologies Ltd. http://www.zend.com/ -- PHP Development Mailing List <http://www.php.net/> To unsubscribe, e-mail: php-dev-unsubscribe@lists.php.net For additional commands, e-mail: php-dev-help@lists.php.net To contact the list administrators, e-mail: php-list-admin@lists.php.net