Jason Wallwork �crivait/wrote: > On July 17, 2002 12:06 pm, you wrote: > > >Can you define what you mean by overhead and provide a quick comparison > > > of Zope overhead vs. PHP overhead? > > > > Zope is daemon that needs to run all the time. PHP only runs when apache > > needs it. > > And how big is this daemon (i.e. memory size)?
On www.linux-quebec.org, apache uses around 4M, and python around 15M. Apache has php loaded as a module. Apache is configured as a proxy for Zope, which runs its own web server. If what you need is speed, then this does not even mean anything. If what you need is low memory usage, then Zope might be a problem for you. But, again, I don't think we need speed or light processes. We just need a solution that fits our needs. IMHO, building a portal in PHP from scratch is not a good idea, unless you really want to spend tens of hours of programming and get a result that still needs hours of work just to add a small functionality. At Linux-Quebec, we chose Zope because it was well-organized, and because we can add and try new components in a matter of minutes. We also looked at PHPNuke and, as with almost all PHP "applications", found that it lacked organization. IMHO, the greatest weakness of PHP is that it's too flat. How do you configure an application? How do you organise your "libraries"? PHP was not made to build applications or portals. It was made for small static web sites that needs just a few dynamic touches. Nicolas --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
