Here we go again...
=:o)
> -----Original Message-----
> From: Berin Loritsch [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, January 09, 2002 8:38 PM
>
>
> Paulo Gaspar wrote:
>
> ...
>
> > Ah! The kind of adaptive caching I recently discussed with Stefano
> > on the Cocoon list!!! I love that!
>
>
> Yes, but unlike Stefano's proposal, the tests are performed outside
> the critical path.
You can always have a thread taking care of cleaning up (more on the
Janitor thing will follow) and measurements must always stay in the
way.
> >>Also, for a cache implementation example, the asynchronous
> >>process will check the
> >>validity of the entries in the Cache, and automatically purge
> >>stale entries. That
> >>way the Cache does not have to perform that check synchronously.
> >>
> >
> > But any cache usually has a "janitor" (using a Cocoon term) to do
> > that.
>
>
> :) Imagine having 20 pools each with their own "janitor" to use the
> Cocoon Store idiom. Each Janitor has it's own thread--that's 20 threads.
I think I saw a Sitemap which syntax/structure suggested a separate
Janitor.
Anyway, that is what I am using: a separate Janitor (Scheduler+ThreadPool)
for several pools. My pool implementation already accepts a Scheduler to
use for running its cleanup stuff.
This way you can have something like this:
<janitor name="my-janitor" .... >
...
</janitor>
<db name="mydb1" janitor="my-janitor" url= ... >
...
</db>
<db name="mydb2" janitor="my-janitor" url= ... >
...
</db>
> My solution has a formal "CommandManager" that allows any Component to
> drop a Command into it's queue and have it executed when the processing
> thread is ready. This allows 1 or maybe even 2 threads handle all
> asynchronous management for all pools.
My ThreadPool just accepts a Runner or Action. I thought I got it from
Avalon too. I am sure it was from somewhere in Jakarta (Commons?).
Isn't that enough?
> By adding the Concept of a PoolManager, we would have one manager for
> n pools. That manager houses all the logic for the managed pools.
What does the PoolManager extra besides the threading stuff?
> > ...
> >
> > The interesting new bit at Avalon is already the ability to
> > serialize back to disk the new/adapted configuration of such
> > adaptive components.
> > =:o)
>
>
> It's not implemented yet, but it will be.
Doesn't the "DefaultConfigurationSerializer" work already?
> > The most interesting bit of dynamic management, for me, is
> > interaction trough some user interface tool. Looking at metrics,
> > changing parameters on the run and saving the configuration
> > with beautiful and easy to use tools... what a nice dream!
> > =:oD
>
>
> That is what Profile (Avalon instrumentation) will allow. I proposed
> to JMeter to have their metering abilities expanded, but for now
> they have not responded to my message. I will repost when I have
> an implementation of Profile in place.
>
> Another piece would be the GUI configuration.
Isn't Peter working on some JMX based tool already?
> <snip>All the other tasty stuff that I need to take alot
>
> of time to review</snip>
=:o)
Have fun,
Paulo Gaspar
http://www.krankikom.de
http://www.ruhronline.de
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
