Result for 09B12A752BB4FA3F56666DE4201CCC13A65095E6

Query result

Key Value
FileName./usr/share/doc/python3-dogpile-cache/README.rst
FileSize3356
MD5CF06286FCC70B9500EA4F4DA9D34DCCA
SHA-109B12A752BB4FA3F56666DE4201CCC13A65095E6
SHA-2562A32D83FBC79CD4B4AFF50ADF491FBB995779DD66AD91BDBBB887AC5C241CCDB
SSDEEP96:g03KDeUWWjtkwLm1zEBdQUyIVh20A6W1QufbYqOYJTLk:g0K6UdOwLEIth276LujTTLk
TLSHT17561623BFB0A17710B9346A5B96651B2EB3E406F77518085909E81F8385AC3583BFDF8
hashlookup:parent-total18
hashlookup:trust100

Network graph view

Parents (Total: 18)

The searched file hash is included in 18 parent files which include package known and seen by metalookup. A sample is included below:

Key Value
MD5A8341E4A0053459A2D5C5817B27B0F21
PackageArchnoarch
PackageDescriptionDogpile 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.
PackageMaintainerCBS <cbs@centos.org>
PackageNamepython3-dogpile-cache
PackageRelease1.el8
PackageVersion0.9.0
SHA-107496BBE5A801C190EEE0740DFC2A253E8686088
SHA-2566D487527AEEA6FA2316203549954990380BB9B17A90CEBC07599BF51397CC2D7
Key Value
MD5DD60029915CF9D70BD32A0DB9D62A565
PackageArchnoarch
PackageDescriptionDogpile 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.
PackageMaintainerFedora Project
PackageNamepython3-dogpile-cache
PackageRelease2.fc32
PackageVersion0.9.0
SHA-10C8CD7B9B09880D9239C3EC5B3A312B64C7533D8
SHA-256499B97BA9F2CF59C1D15F7955F97C9881CE2522BBD100F9634C8485B1C799C26
Key Value
MD5DDB083C4B36120D71576F16C6F76F55E
PackageArchnoarch
PackageDescriptionDogpile 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.
PackageMaintainerFedora Project
PackageNamepython2-dogpile-cache
PackageRelease1.el8.1
PackageVersion0.6.8
SHA-10F7652B9674CF2F2C593B40DAD17D7FB7C0623CB
SHA-2565043A90EBE9CB7DFEDC7D354DC347A2845081C6BC9A81DD9ECAAB673CCAB9904
Key Value
MD560E7E993DD90F33D7103E6B7EF2E8294
PackageArchnoarch
PackageDescriptionDogpile 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.
PackageMaintainerpterjan <pterjan>
PackageNamepython2-dogpile-cache
PackageRelease1.mga7
PackageVersion0.6.8
SHA-11ECBA2CB82059A2DC27F9CE9EDC77C5F98889E8D
SHA-256796F729DD28FBC2DF7A020B9368835594661989959E8C561F61BB2AF9282A4B8
Key Value
MD5B2454FEEF3375E5F0FE00FE248D47F66
PackageArchnoarch
PackageDescriptionA 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.
PackageNamepython2-dogpile.cache
PackageRelease1.2
PackageVersion0.7.1
SHA-1297F16B0920C88238E14F8B90F1C2C80A110AB66
SHA-256106E3E5F4B1A35AA5940EA62F22E1F9409FB954BE6F42065AF8164803291C2BC
Key Value
MD564C899443E4FE1329846AFA38F21655D
PackageArchnoarch
PackageDescriptionA 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.
PackageNamepython3-dogpile.cache
PackageRelease2.4
PackageVersion0.9.0
SHA-12BFBFE659FF5552CD1E50BD7886B68BED5020850
SHA-256A6CD0967F3E7A13C5BF58BBBE177B90BB395D118D403899F86CEE77F13BDA6D2
Key Value
MD57C72D313A5069226A8F423C83E076E22
PackageArchnoarch
PackageDescriptionDogpile 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.
PackageMaintainerFedora Project
PackageNamepython3-dogpile-cache
PackageRelease1.el8.1
PackageVersion0.6.8
SHA-134634E83B2BA877C077008A5DF85677E22A916CA
SHA-256EA155B509983EB0CFF027E1E020F3C0944B1ABBA578F5C7A23F1AA0FAFFB0954
Key Value
MD5542FF1DAF5193670182DAA22414FD9A5
PackageArchnoarch
PackageDescriptionA 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.
PackageNamepython2-dogpile.cache
PackageReleaselp150.2.2
PackageVersion0.7.1
SHA-1426189BC4EE5A099310DF95F0816EAFF452079C1
SHA-2563A1D4341FFAAEFF71E7C579139709E141A95C55314FFD537DF32ACB76E2D9814
Key Value
MD55CD5004365419C550794633EA063BBCD
PackageArchnoarch
PackageDescriptionA 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.
PackageNamepython3-dogpile.cache
PackageRelease1.2
PackageVersion0.7.1
SHA-143799CDE338CCFDC7981C60C103D41267551DC91
SHA-256B410656CADE41F4F02C918866E7E2CFFA09916F389CB89AD39719F84A8699013
Key Value
MD5BE57B4EFC0604DD5764ED7B90EAC1660
PackageArchnoarch
PackageDescriptionA 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.
PackageNamepython3-dogpile.cache
PackageReleaselp151.1.2
PackageVersion0.7.1
SHA-14A8EEFC05238BDC844948EECDBCC22529DA4F300
SHA-256F9B025CCD3E5F8A53195AE55D945A3142BE0EC5BEBE0CEDC48C3DFF7B58A5E2B