Models

Urls are extracted from models instances on post_save signal. Two sources are used:

• instance.get_absolute_url(), if it exists

• instance.get_purge_urls(), if it exists. The application expects a list of absolute paths similar to what is provided by get_absolute_url().

Purge request is sent when response has been computed: if an exception occurs the urls are not purged. Purge requests are asynchronous: worker threads handle that so that we don’t have wait to complete all requests before returning the response.

Cache configuration

The cache must be configured to accept and handle “PURGE” requests from the server where the django application is hosted.

Homepage, code, bug tracker

• Homepage: http://launchpad.net/django-cachepurge

• Code repository: http://code.launchpad.net/django-cachepurge

• Report bugs at http://bugs.launchpad.net/django-cachepurge

0.3 - 2011-04-01

• Compatible with Django 1.3: don’t import django.utils.thread_support

• catch NoReverseMatch exception when trying to find an instance’s url

0.2 - 2010-11-22

• Accept to purge only site urls, converted if needed into their relative form (i.e, “/some/path/”)

0.1a - 2009-05-25

• 0.1a: 0.1 released missed some files

• Initial release