Key | Value |
---|---|
FileName | ./usr/share/doc/python-dogpile.cache-doc/html/api.html |
FileSize | 267618 |
MD5 | DB34523F115096E83C1E3F6EE86FC36E |
SHA-1 | 38292F71B067A888C23DBDAD2DA8FFF1D9F4E5F5 |
SHA-256 | 6DE1FB2462D63E88C397F8713412E58E951610BCA609FB247655B4DFF046E162 |
SSDEEP | 6144:QgBEMd5EhPhAAOQGSJIuS7SxZSrS9SXOad:tD |
TLSH | T1DB44CEAAA5F64A3309B385DAA3BA0B76F4EA401EF1510450E6FD936C83CDD84751BC3D |
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 | 66540 |
MD5 | 8D851C7ED488D8054227E34A4B6C0E34 |
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 | 1.0.1-0ubuntu1 |
SHA-1 | ADA77BCE81829132BA81EAA396799D2A986AA8AF |
SHA-256 | 3370CC43759CC072601A989ABDD9B00CC5C6FBD431EB014C4573803806A670D6 |