I am building a zope based application to manage the (medium) volume delivery of a large number of what are essentially static documents from a central server. The server itself is a Win2003 server -- I think with 3.x Mhz cpu, 1 gbyte of memory and reasonably fast hard disks but I don't have full control over it. It is only being used as a zope server -- no other requirements. I have no control of upstream caching ( though there are caches strategically deployed in this corporation to manage bandwidth usage). I am looking at local caching options available in Zope 2.6.2 (Ram Cache, Accelerated HTTP Cache) and am not sure I understand the purpose and usage of those products. Is it likely that I will be better off using no local caching? If one of the standard Cache products is recommended how do I configure it? How are elements associated with the cache? Can I locate the cache in a "sub directory" and have it cache all elements below it in the hierarchy automatically.
Brian Sullivan wrote at 2004-1-3 12:44 -0500:
... I am looking at local caching options available in Zope 2.6.2 (Ram Cache, Accelerated HTTP Cache) and am not sure I understand the purpose and usage of those products.
The "HTTP Cache" manager sets HTTP cache headers for requests. This allows external HTTP caches (usually, there is one in the browser; there may be caches in between, either set up by yourself or another). Unless you use high end features of Squid, the HTTP cache approach can only cache complete requests. A RAM Cache can cache page components (i.e. it has smaller granularity than the HTTP Cache approach). Thus, you use an "HTTP cache" to cache complete requests and a "RAM cache" to cache pieces that are combined into full pages by some non cached device... -- Dieter
participants (2)
-
Brian Sullivan -
Dieter Maurer