mathieu wrote: > The CacheInvalidation issue being tackled here is solely related to > the current database-backed implementation of the caching API.
Just one clarification: the cache we are talking about cannot be defined as database-backed. The database is the primary data storage, and we cache some of that data in memory. At this point, we are not talking about caching e.g. generated HTML pages or anything like that (yet). > The Django caching system implementation is very neat and can be seen > here : http://code.djangoproject.com/browser/django/trunk/django/core/cache The links to Django are very interesting, thanks for the pointers. > What do you think of a little refactoring allowing different caching > backends to be used ? Don't that seem a good candidate for a plugin > extension point ? That's a good idea. About that CacheInvalidation page, my plan is to create and test a prototype of "Idea 1" with an in-memory cache, no additional dependencies, and no extension point, more or less the simplest possible implementation. If it works out well, and is committed to trunk, I would like to investigate modularizing the cache backend, and have a look at memcached as a second backend. -- Remy
signature.asc
Description: OpenPGP digital signature
