Edgewall Software

Changes between Version 4 and Version 5 of TracDev/Proposals/CacheInvalidation


Ignore:
Timestamp:
Mar 6, 2009, 10:00:05 PM (15 years ago)
Author:
Remy Blank
Comment:

Added comments.

Legend:

Unmodified
Added
Removed
Modified
  • TracDev/Proposals/CacheInvalidation

    v4 v5  
    9898
    9999The open problem I see as well is about maintaining a coherent view from the cache during the lifetime of a given request. That might indeed be another argument in favor of a dedicated component with a more advanced cache logic. Anyway, the patch above is at least a first step that seems to work fine in my testing.
     100
     101''Indeed, the basic idea is the same. My goal was to push as much of the logic into the `CacheManager` as possible, so that cache users would only have two functionalities: get the data (this could even be hidden by using a `property`-like descriptor) and invalidate the cache. There should be no need for cache users to "remember to first check if the cache is valid, then ...": this logic is common to all cache users, and can be integrated into the cache manager.''
     102
     103''I'll get started on a prototype implementation as well, to see how simple I can make it for the cache user.''