Am 30.12.2005 um 03:11 schrieb Stephen Deasey:
Still to think about are per-thread Tcl caches. The main reason for
these are that you can put Tcl objects in the cache, not just their
string rep, which is particularly useful for already-compiled byte
code -- i.e. for *.tcl pages.
The best solution for caching byte code might be to share the
mechanism with ADP pages. They currently have a pre-thread cache of
script blocks, and a per-server cache of text blocks, for each page.
AOLserver 4.5 adds a per-server output cache. We could use this for
*.tcl pages as well, perhaps negating the need for per-thread Tcl
caches. That still leaves Tcl objects like lists or dictionaries that
you may not want to stringify on each access.
Input welcome...
Hmhmhmhm... those adp caches are pretty-much app-dependent (adp), right?
OTOH, the cache module is absolutely generic: put X in, get X out
whatever X is, or?
We do not have any use for that. If I need such thing, I create a
namespaced
array and stuff things there. Admitently, this is not a real cache where
things are expired, but during the (short) connection lifetime I do
not have
that many things I'd like to keep arround...
I don't know... If anybody has the need to make this beast, feel free to
do that. I'm perfectly happy with the global cache as-is now.
Cheers
Zoran
