You're right about caching, Jens. Nonetheless I talked about the performance, considering every page responding to a unique and personalized request. If there are workarounds to cache that, I'll be happy to know about them. :) Ausum
I came up to the idea that for people wanting to use Zope for high trafficked sites, and thus are looking for every bit of performance out of their web applications, ZPT would probably may not be a choice at all.
I've recently tested Plone (the CMF skin built entirely of ZPTs) on a Pentium IV @ 1.7GHZ plenty of memory, and generally speaking I had this sensation that in despite of that horsepower, every page took a little bit of time to render while some pages took from half a second to two seconds. (DTML based pages, no matter how complicated they were, rendered almost immediately ). Now, take that and multiply it for 20 or more simultaneus hit responses and you'll find out that you'll need more horsepower than the average in order to provide a pleasant session for all the users.
you'll find that you need *caching*. no large-scale application server can provide hundreds of hits a second without a good cache in front of it and without making sure that the rendered content carries the right caching headers.
jens
_______________________________________________ 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 )