Forum OpenACS Development: Problem with cache UI
I've stumbled in a problem while trying to look into cached keys on my development server. It comes from a cvs update two days ago.
An example page is /acs-admin/cache/show-util-memoize?pattern=util , that should return an error because the
proc looking for the keys doesn't return their timestamp anymore when called on Naviserver.
I've done some research and found there have been some big changes in caching system around september, and now cache on Naviserver is handled by a new native api.
Procs retrieving cache values on Naviserver behave differently from those defined on Aolserver. As I could see from comments in the code, this is something you are aware of.
What I ask is: is there already a plan about UI for the two servers? Is this going to fork? Why can't we just get the timestamp from the new api and mantain the same behavior?
i guess, this slipped through, since this user interface is limited to the util_memoize cache only, and people use different interfaces. I've added compatibility for NaviServer (committed to the oacs-5-8 branch).
Is it still ok to use it, or you're going for a different preferrable idiom? If so, what is it?
That is one of the reasons, why e.g. xotcl-core/xowiki use different caches.
These locking problems show only up for large and busy sites, for small sites, this does not matter.