Products.StandardCacheManagers · PyPI
source link: https://pypi.org/project/Products.StandardCacheManagers/
Go to the source link to view the article. You can view the picture content, updated content and better typesetting reading experience. If the link is broken, please click the button below to view the snapshot at that time.
Project description
Overview
This package provides two cache managers for Zope. A RAMCacheManager and an Accelerated HTTP cache manager, which adds HTTP cache headers to responses.
The following is intended for people interested in the internals of RAMCacheManager, such as maintainers.
Introduction
The caching framework does not interpret the data in any way, it acts just as a general storage for data passed to it. It tries to check if the data is pickleable though. IOW, only pickleable data is cacheable.
The idea behind the RAMCacheManager is that it should be shared between threads, so that the same objects are not cached in each thread. This is achieved by storing the cache data structure itself as a module level variable (RAMCacheManager.caches). This, of course, requires locking on modifications of that data structure.
Each RAMCacheManager instance has one cache in RAMCacheManager.caches dictionary. A unique __cacheid is generated when creating a cache manager and it’s used as a key for caches.
Object Hierarchy
RAMCacheManager RAMCache ObjectCacheEntries CacheEntry
RAMCacheManager is a persistent placeful object. It is assigned a unique __cacheid on its creation. It is then used as a key to look up the corresponding RAMCache object in the global caches dictionary. So, each RAMCacheManager has a single RAMCache related to it.
RAMCache is a volatile cache, unique for each RAMCacheManager. It is shared among threads and does all the locking. It has a writelock. No locking is done on reading though. RAMCache keeps a dictionary of ObjectCacheEntries indexed by the physical path of a cached object.
ObjectCacheEntries is a container for cached values for a single object. The values in it are indexed by a tuple of a view_name, interesting request variables, and extra keywords passed to Cache.ZCache_set().
CacheEntry is a wrapper around a single cached value. It stores the data itself, creation time, view_name and keeps the access count.
Changelog
4.0.3 (2019-10-14)
- more package cleanups
- cleaned up ZMI views for Zope 4
- fixed several errors due to changed behavior in Python 3
4.0.2 (2019-02-17)
- Specify supported Python versions using python_requires in setup.py
- Added support for Python 3.7 and 3.8
- Dropped support for Python 3.4 as Zope does not support it anymore
- More PEP8 compliance.
4.0.1 (2017-05-23)
- Move version dependency to a released version of Zope
4.0.0 (2017-05-13)
- Require Zope 4.
- Python 3-compatibility
3.0 (2016-07-18)
- Remove HelpSys support.
2.13.1 (2014-09-14)
- Prevent warnings when RAM caching in a context without a Request.
2.13.0 (2010-07-11)
- Released as separate package.
Hashes for Products.StandardCacheManagers-4.0.3-py2.py3-none-any.whl
Hashes for Products.StandardCacheManagers-4.0.3-py2.py3-none-any.whl Algorithm Hash digest SHA25618cc419a08bb0c6d67540b426d9e8b902429695eb60ac823c4a0d7d20c0cae4b
MD5
8b156156fdfcd4c9042104b7b3a5981b
BLAKE2-256
8af3da1c226849940cf302710723b231b5c5cae854c14be6e9a116fa6b89dbe9
Hashes for Products.StandardCacheManagers-4.0.3.tar.gz
Hashes for Products.StandardCacheManagers-4.0.3.tar.gz Algorithm Hash digest SHA256de91522fe1d27adc4bd61d5910eeafc2dbb85042ca35a2730c6982ea18eedad8
MD5
dd9dc682572abc29072b395a93816efb
BLAKE2-256
393eb922b348d10158e2a94badf45f798b1b654a8a02841d0c21f0333a83c3c7
Recommend
About Joyk
Aggregate valuable and interesting links.
Joyk means Joy of geeK