Skip to main content

Cache rendered pages including headers

Project description

Introduction

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

Installation

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.

Changelog

1.2 - 2008-01-16

  • Repackage PageCacheManager is a python egg. [wichert]

Project details


Release history Release notifications

This version
History Node

1.2

Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Filename, size & hash SHA256 hash help File type Python version Upload date
Products.PageCacheManager-1.2-py2.4.egg (21.4 kB) Copy SHA256 hash SHA256 Egg 2.4 Apr 16, 2008
Products.PageCacheManager-1.2.tar.gz (12.3 kB) Copy SHA256 hash SHA256 Source None Apr 16, 2008

Supported by

Elastic Elastic Search Pingdom Pingdom Monitoring Google Google BigQuery Sentry Sentry Error logging AWS AWS Cloud computing DataDog DataDog Monitoring Fastly Fastly CDN DigiCert DigiCert EV certificate StatusPage StatusPage Status page