This is a pre-production deployment of Warehouse, however changes made here WILL affect the production instance of PyPI.
Latest Version Dependencies status unknown Test status unknown Test coverage unknown
Project Description


PageCacheManager is designed to speed up access to content views while at the same time making sure that stale content is not served up.


PageCacheManager is designed specifically for caching views of content objects. Unlike RAMCacheManager, PageCacheManager caches both the html generated by a view as well as the HTTP headers.

PageCacheManager builds upon Zope’s standard cache manager machinery. As with RAMCacheManager, you associate some page templates with the cache manager and configure the properties. PageCacheManager requires an extra step: content to be cached must generate an ETag via a caching policy. PageCacheManager looks for a CachingPolicyManager with id caching_policy_manager. If it finds it, it then gets an ETag for the current template + content object combination. This ETag is then used as the index into the cache. If you don’t have an ETag generated for your content, your pages will not be cached.

If you create an ETag that changes when the content is changed, then the content served up by the cache will stay fresh. There will be a cache miss the first time the page is hit after the ETag changes, then subsequent hits to the newly modified content view will reflect the new version. If your content view is personalized, you will want your ETag to vary depending on the current user. A good ETag with these properties is as follows:

ETag = id of currently authenticated user + delimiter + last modified time
for content + delimiter + current time rounded to the nearest hour

The use of the id in the ETag means that every user’s view of a content object will have a different ETag, so everybody will get different cached objects. The use of the modification time means that every time the content object changes, it will generate different ETags and hence will result in new copies being pulled from the cache. The use of the current time rounded to the nearest hour means that nothing will be served up by the cache for more than an hour.

Added bonus: PageCacheManager handles conditional GETs. If the incoming request has an If-Modified-Since header with an ETag that matches the content object’s current ETag, PageCacheManager will set a status 304 header (Not Modified) and will return no content.


1.2 - 2008-01-16

  • Repackage PageCacheManager is a python egg. [wichert]
Release History

Release History


This version

History Node

TODO: Figure out how to actually get changelog content.

Changelog content for this version goes here.

Donec et mollis dolor. Praesent et diam eget libero egestas mattis sit amet vitae augue. Nam tincidunt congue enim, ut porta lorem lacinia consectetur. Donec ut libero sed arcu vehicula ultricies a non tortor. Lorem ipsum dolor sit amet, consectetur adipiscing elit.

Show More

Download Files

Download Files

TODO: Brief introduction on what you do with files - including link to relevant help section.

File Name & Checksum SHA256 Checksum Help Version File Type Upload Date
Products.PageCacheManager-1.2-py2.4.egg (21.4 kB) Copy SHA256 Checksum SHA256 2.4 Egg Apr 16, 2008
Products.PageCacheManager-1.2.tar.gz (12.3 kB) Copy SHA256 Checksum SHA256 Source Apr 16, 2008

Supported By

WebFaction WebFaction Technical Writing Elastic Elastic Search Pingdom Pingdom Monitoring Dyn Dyn DNS HPE HPE Development Sentry Sentry Error Logging CloudAMQP CloudAMQP RabbitMQ Heroku Heroku PaaS Kabu Creative Kabu Creative UX & Design Fastly Fastly CDN DigiCert DigiCert EV Certificate Rackspace Rackspace Cloud Servers DreamHost DreamHost Log Hosting