Changes between Version 99 and Version 100 of Dev/Technical/ZEO
- Timestamp:
- 02/10/12 12:08:15 (16 months ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Dev/Technical/ZEO
v99 v100 63 63 When the client is connected to the server, it receives invalidations every time an object is modified. 64 64 If the cache is Persistent, when the client is disconnected then reconnects, it must perform cache verification to make sure its cached data is synchronized with the storage's current state. 65 66 As of 2012, this cache can only be used one process at a time, which apparently renders it useless if your processes are persistent and you have enough memory to spare. See [https://mail.zope.org/pipermail/zodb-dev/2010-October/013737.html|this thread] for some more info. 67 65 68 === 3.2 ZEO Client cache's strategy === 66 69 The ZEO Client cache uses a FIFO strategy. In others words there is a pointer inside the cache that goes around the file, circularly, forever.
