antidogpiling 1.1.1

Generic and specific implementations of anti-dogpiled caching

=============
antidogpiling
=============

The antidogpiling framework is a generic set of functionality for implementing anti-dogpiled caching. It currently includes completed implementations for all the Django 1.2 and 1.3 cache backends.

Dogpiling is the effect you get when a cached value times out, and everyone rushes to create a new value. The anti-dogpiling tries to mitigate this by serving the old value while waiting for a few (ideally one) who are let through to produce a new value.

Benefits of this package:

- It provides the generic functionality
- It wraps the cached data in a custom object and not in a tuple or dict or so, making it possible to actually cache tuples or dicts which would potentially conflict with the internal handling
- It supports all Django 1.2 and 1.3 cache backends, without re-implementing any Django functionality

Using the anti-dogpiled Django 1.2 backends
===========================================

Simply set the ``CACHE_BACKEND`` setting to point to the right module. A few examples::

CACHE_BACKEND = 'antidogpiling.django.memcached://127.0.0.1:11211/'
CACHE_BACKEND = 'antidogpiling.django.filebased:///var/tmp/django_cache'

Using the anti-dogpiled Django 1.3 backends
===========================================

Simply replace the ``BACKEND`` reference with the corresponding anti-dogpiled backend. An example::

CACHES = {
'default': {
'BACKEND': 'antidogpiling.django.memcached.MemcachedCache',
'LOCATION': '127.0.0.1:11211'.
}
}

Change history
==============

1.1.1 (2011-05-29)
----------------

* Added support for Django 1.3 backends

1.0.1 (2011-02-02)
------------------

* Added manifest file for proper packaging

1.0 (2011-02-02)
----------------

* Initial version