I agree... I saw a message on this list a few days back where someone mentioned Apache in front of Squid, which totally left me scratching my head in confusion... Squid+ESI should be pretty powerful. Since ZPT will do XML namespaces, ESI should be supported without any issues, if you wanted to do this out of the box (of course, you still would need to patch and compile Squid with the ESI support). One other thing that Apache can't do (without mod_backhand, I think???) is truly load-balance, but Squid can with Zope 2.6+ (thanks to ICP support): Squid treats ZEO nodes as cache peers and removes them if they are down, and also directs traffic according to load (updated constantly as function of response times). Sean -----Original Message----- From: Dieter Maurer [mailto:dieter@handshake.de] Sent: Tuesday, November 05, 2002 11:56 AM To: Ausum Studio Cc: zope@zope.org Subject: Re: [Zope] Apache-Squid-Zope, Squid-Apache-Zope.. or just Squid-Zope? Ausum Studio writes:
I know this has been treated before, but as much as I can see, people use the three ways with apparent success. Within the context that ZC is funding Squid to implement ESI, would any member of the community try a theoretical resume (not a how-to) of the issues regarding using Squid to cache Zope? Which one of the three combinations is the best? I would go for Squid+Zope only. Why use an additional component (Apache), when it is not necessary?
Dieter _______________________________________________ Zope maillist - Zope@zope.org http://lists.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope-dev )