[Zope] Brainstorm: Zope behind proxying cache?

[Jonathan]

>Once you really absorb the possibilities and practices of a tool like Zope
>or PHP, though, you begin to see your site as a collection of templates and
>interfaces, combining static snippets with data queries and views.  It
>makes no more sense to cache many of the pages from such a site than it
>would to cache windows from an accounting program or word processor.
>You're moving into the land of the web application.

The client still gets a page, so it depends on the kind of content 
you have and the functionality you want to offer to visitors.

If the main reason you need a dynamic tool is because you are working 
on the same site with a number of different people, you'll need 
advanced content management tools as soon as it is finished it can be 
static, no problem there. When it changes, republish it.

If you need a dynamic tool because you've got a lot of data that is 
poured into a template when a client requests a page or queries the 
database through a form, then it makes sense to generate a page on 
the fly everytime someone requests it.

The major difference between a web application and one that runs on 
the local machine is speed. The code necessary for drawing windows on 
a screen is cached in RAM on the local machine and therefore very 
fast. A page is not.

Cya
Jonathan

--
UR Communications - Solutions for a wired world
Who, what & where @ http://www.ur.nl/