Jim Fulton wrote:
Amos Latteier wrote:
(snip)
I would like to add that the response generated by some objects depend on the user. So for example we wouldn't want to cache DTML Methods which display different data depending on the roles of the user who accessed the page.
These are probably pages that don't want to be cached.
or that want to be cached with an url (key) that includes the role and/or AUTHENTICATED_USER.
OK, maybe this can be abstracted to say that caching could be tied to request environment variables, such as "AUTHENTICATED_USER", and "PATH_INFO".
And cookies....Ugh.
Maybe we can just attach some callback mechanisms to variable lookups which, among other things, also invalidate cache or change/lookup_new cache key ?
I imagine that there might be a knob that a content manager or programmer could use to give Zope some hints in this regard.
Like the cacheing time for SQL Methods ? -------------------- Hannu