Key | Value |
---|---|
FileName | ./usr/share/doc/python-dogpile.cache-doc/html/api.html |
FileSize | 255495 |
MD5 | 1E7E4E579F56FC02F1C93B453AE547B0 |
SHA-1 | 07ADFB69B24F4D856EF073FD683BDFD8393971F9 |
SHA-256 | 7F580B580CD006E052C95FAFE51C10C7F4DF7A32A408C07F90BAE3CE232E3A66 |
SSDEEP | 6144:iABRZ39cFShAxL/hS+zOS0SGRSbSESqOaR:7k |
TLSH | T17744DCAAA5F64A3309B385DAA3BA0B35B5EA441EF5910050E6FDC36C83CDD84751BC3D |
hashlookup:parent-total | 1 |
hashlookup:trust | 55 |
The searched file hash is included in 1 parent files which include package known and seen by metalookup. A sample is included below:
Key | Value |
---|---|
FileSize | 68632 |
MD5 | 3E7367B1647EED64D9BA892BBC527CF5 |
PackageDescription | caching front-end based on the Dogpile lock - doc A caching API built around the concept of a "dogpile lock", which allows continued access to an expiring data value while a single thread generates a new value. . dogpile.cache builds on the dogpile.core locking system (see http://pypi.python.org/pypi/dogpile.core), which implements the idea of "allow one creator to write while others read" in the abstract. Overall, dogpile.cache is intended as a replacement to the Beaker (see http://beaker.groovie.org) 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. . This package provides the documentation. |
PackageMaintainer | Ubuntu Developers <ubuntu-devel-discuss@lists.ubuntu.com> |
PackageName | python-dogpile.cache-doc |
PackageSection | doc |
PackageVersion | 0.7.1-1ubuntu1 |
SHA-1 | A8963AE039B142F1DF05150B3F15C8BB3D0A381C |
SHA-256 | 66AA9CD7FE2D35B28713C2262F53ACC14E6530866E4F814D72B04BBE84E4011E |