On Thu, 16 Nov 2000, Dave Bryson wrote:
> Jason,
>
> What do you mean by this -
>
> // This is an ObjectExpiredException, but
> // I don't want to try the structure of the
> // caching system to the Runtime.
>
> What's the problem with tying to the Cache system?
I probably jotted that down at some point quickly.
I was thinking to access the cache at a single point
and catch just the general Exception so that all
the Runtime had to know about was the GlobalCache
and nothing of it's internals if possible.
Right now that caching code isn't being used
inside the Runtime. I was thinking of trying
to make a general cache: permanent objects,
expirable object, refreshable objects. The permanent
objects would be managed externally like the template
cache where the Runtime figures out whether the
template needs to be reloaded. They wouldn't expired or
be refreshed automatically.
I was thinking that of making a single cache that could
deal with all cases and then optimize the snot
out of it, if at all possible.
--
jvz.
Jason van Zyl
[EMAIL PROTECTED]
