Key | Value |
---|---|
FileName | ./usr/share/doc/python-dogpile.cache-doc/html/api.html |
FileSize | 273865 |
MD5 | BCEF1A6BE1ADBBD25B510A31B19095AA |
SHA-1 | 27435C12119441A26B47F1564FB21EDA8D048742 |
SHA-256 | 9621C35EFC28F918BB46E08680A324E95CB82C8897C966B1966FEDAF1E0C4C36 |
SSDEEP | 6144:WSBEvd5NukhR9/aFS8fuShSVhS7SaSVOaf:kt |
TLSH | T1D344ADAAA5F64A33097385DB93BA0B76B4EA401EF1910450E6FD93AC83CDD84751BC3D |
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 | 89976 |
MD5 | 28489731884A59C9C8BC4D9C8F937777 |
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 | Debian OpenStack <team+openstack@tracker.debian.org> |
PackageName | python-dogpile.cache-doc |
PackageSection | doc |
PackageVersion | 1.0.2-2 |
SHA-1 | 89ADB1C0C05617C504D808218D25509A68D7AD4C |
SHA-256 | 379BF1E98DCDFEABB82F56A31F2068CDA60FB48FD885FF71113902E207CCCC79 |