Re: Excalibur Cache

[Eung-ju Park <co...@hotmail.com>]

Is it really needed?

validate cached item when get().
or
validate cached items when some time.
What is difference?

----- Original Message -----
From: <sh...@acedsl.com>
To: <co...@apache.org>
Sent: Wednesday, June 19, 2002 7:34 AM
Subject: Excalibur Cache


> I need a feature in the cache which I didn't see on a quick pass through
the
> API.  I would like a self-purging cache, which will remove() records when
they
> exceed their lifespan.  I see you have a TimeoutValidator, and basically
just
> want to have a PurgeController object which will run a purge routine on a
> regular interval which simply TimeoutValidates all entries in the cache.
There
> is no reason why the purge routine should not be able to use any
Validation
> object for the purge.  I would be happy to take a crack at this myself,
and
> wanted to know if you would be interested in brainstorming the UML of the
> additional classes first.  I am contacting you directly initially just to
keep
> things simple, but am also happy to post the same message to the Excalibur
Dev
> listserv.
>
> Shawn Hainsworth
> -------------------------------------------------
> This mail sent through AceDSL WebMail (http://webmail.acedsl.com)
>

--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>

Re: Excalibur Cache

[Eung-ju Park <co...@hotmail.com>]

----- Original Message -----
From: "Berin Loritsch" <bl...@apache.org>
To: "'Avalon Developers List'" <av...@jakarta.apache.org>
Sent: Wednesday, June 19, 2002 9:41 PM
Subject: RE: Excalibur Cache


> > From: Eung-ju Park [mailto:colusvi@hotmail.com]
> >
> > Is it really needed?
> >
> > validate cached item when get().
> > or
> > validate cached items when some time.
> > What is difference?
>
>
> The difference is in the cost of using the cache.
> If the cache validation is asynchronous, you don't
> have to check the resource every time you get() it.
> You can also lower the number of times it is checked.
>
> Asynchronous management shortens the critical path
> by an order of magnitude.

Validation is must be execute before get cached item.
Async validation reduce invalid cached item when get() is called. But I
think it is small effect.
Cache is not useful when high invalid cached item ratio.

>
>
> --
> To unsubscribe, e-mail:
<ma...@jakarta.apache.org>
> For additional commands, e-mail:
<ma...@jakarta.apache.org>
>
>

--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>

RE: Excalibur Cache

[Berin Loritsch <bl...@apache.org>]

> From: Eung-ju Park [mailto:colusvi@hotmail.com] 
> 
> Is it really needed?
> 
> validate cached item when get().
> or
> validate cached items when some time.
> What is difference?


The difference is in the cost of using the cache.
If the cache validation is asynchronous, you don't
have to check the resource every time you get() it.
You can also lower the number of times it is checked.

Asynchronous management shortens the critical path
by an order of magnitude.


--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>