Ok so I figured cache invalidation was a royal pain in the arse, and that one of the current best ways is to cache infinitely and only invalidate when the associated data is stale. But! How do we know when it is stale?
Effectively the point of this project is to give you a way to formally define caches with meta information such as other caches they depend on (so you can do the “Russian Doll” style caching that 37 Signals went on about), models that caches directly depend upon, other models that might invalidate the cache, and other useful stuff.
There are several other concepts that I thought up too, such as “hooks”.
Of course I will expand the documentation because this project is blatantly really useful for defining a decent caching scheme instead of shitting out some half baked attempt that confuses people and gives everyone stale data all the time.
To-Do
Template tags to access HTML templates.
Documentation
Tests
Sorting out how best to trick fucking python-memcached into doing infinite caching.
1 maintainer
Metadata
1 maintainer
Release files for django-babylon 0.1.13
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| django-babylon-0.1.13.tar.gz | 4.0 kB | Details |
Release files / django-babylon-0.1.13.tar.gz
| Download URL | django-babylon-0.1.13.tar.gz |
|---|---|
| Size | 4.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
63c8980fb29cae4ccaea9dac12b83b839d09eccabea335456719a9dbbb23ab6c
|
|
BLAKE2b-256 checksum How to use checksums |
e162e66fc96000b5913395c80ccb13f9348f519278b2abb3002df89da257b267
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
