A caching front-end based on the Dogpile lock
Dogpile consists of two subsystems, one building on top of the other. dogpile provides the concept of a "dogpile lock", a control structure which allows a single thread of execution to be selected as the "creator" of some resource, while allowing other threads of execution to refer to the previous version of this resource as the creation proceeds; if there is no previous version, then those threads block until the object is available. dogpile.cache is a caching API which provides a generic interface to caching backends of any variety, and additionally provides API hooks which integrate these cache backends with the locking mechanism of dogpile. Overall, dogpile.cache is intended as a replacement to the Beaker caching system, the internals of which are written by the same author. All the ideas of Beaker which "work" are re- implemented in dogpile.cache in a more efficient and succinct manner, and all the cruft (Beaker's internals were first written in 2005) relegated to the trash heap.
Release | Stable | Testing |
---|---|---|
Fedora Rawhide | 1.3.1-3.fc41 | - |
Fedora 41 | 1.3.1-3.fc41 | - |
Fedora 40 | 1.3.1-1.fc40 | - |
Fedora 39 | 1.2.2-3.fc39 | - |
Fedora EPEL 9 | 1.2.2-2.el9 | - |
Fedora EPEL 8 | 0.6.8-1.el8.1 | - |
You can contact the maintainers of this package via email at
python-dogpile-cache dash maintainers at fedoraproject dot org
.