./devel/py-dogpile-cache, Caching front-end based on the Dogpile lock

[ CVSweb ] [ Homepage ] [ RSS ] [ Required by ] [ Add to tracker ]

Branch: pkgsrc-2018Q2, Version: 0.6.4, Package name: py27-dogpile-cache-0.6.4, Maintainer: pkgsrc-users

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.


Required to run:
[devel/py-setuptools]

Master sites:

SHA1: 437ecf8f6ac7bd03d54c2067f065fba1727617a7
RMD160: 73dd2ae9d9dce936849eb21441ef35b1d7f5ae71
Filesize: 308.138 KB

Version history: (Expand)