I think, in theory, you can do ESI in Zope now, you just need to use a patched Squid in front of Zope, use well-formed XHTML with embedded ESI, and set appropriate HTTP headers (Surrogate control header) manually so that ESI is parsed on the client-connection end of Squid. I haven't used this, but I bet this would work. I think the only requirement is well-formed xml for your templates. What future Zope versions would theoretically add is a way to detect esi usage in a ZPT and set the header for you automatically. Sean -----Original Message----- From: Dylan Reinhardt [mailto:zope@dylanreinhardt.com] Sent: Tuesday, February 18, 2003 3:10 PM To: sean.upton@uniontrib.com Cc: zope@zope.org Subject: RE: [Zope] Superfast PageTemplates: Call for expertise At 02:55 PM 2/18/2003, sean.upton@uniontrib.com wrote:
In know this is purely speculation, but what about caching page-templates in some intermediate format like ESIS, and writing a lexical scanner for the TALES structure in C/Flex with callbacks to Python for code evaluation and object traversal?
You could probably do 90% of that by stuffing layout fragments into RAM Caches and Session data... and then you could assemble the whole thing on the fly using DTML... oh, wait. :-) More seriously, it'll be great when the ZC/Squid ESI project becomes available. That should serve this purpose nicely. Dylan _______________________________________________ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )