Sebastien,
>Gerhard Froehlich wrote:
>> 
>> >From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On
>
>[OT: your mailer is broken, it use wrong field]
>
>> >So I probably do not have the main StoreJanitor.
>> 
>> There is only one impl, yet ;-).
>> On my machine the StoreJanitorImpl initialize proper.
>>
>> >I'm going to write a static (synchronized) StoreJanitor to
>> >record any in-memory Store created.
>> >Is it a good solution, or is there something better ?
>> 
>> Why, the actual StoreJanitorImpl does this already. But maybe
>> I understood your question wrong.
>
>There is only one implementation, but I thought I got a new instance
>of it. I tested and it's ok, there is one and only one instance.

Yes because the StoreJanitorImpl implements the ThreadSafe interface. 
"A Component that implements this interface will generally only have 
one instance available in the system, and other Components will use
that one instance." (Avalon Developer Guide)

>
>> >Second:
>> >
>> >Everybody want to know what is inside, isn't it?
>> >Here is another patch to display classname of cached object...
>> >
>> >And surprise, there is nothing in our Stores!
>> >When I request an Object by his key, I have nothing most of the
>> >time!
>> 
>> Yes because default we're using the NonCachingxxxPiplines (I don't
>> know the reason, really!).
>> Change in the cocoon.roles the roles for StreamPipline and EventPipeline
>> to CachingStreamPipeline and CachingEventPipeline. Then it should
>> work proper.
>>
>> >Why does we store null values in MRUMemoryStores ?
>> 
>> Don't know.
>
>With all thoses null values, finding a key is probably slower.

Sorry through some other business I'm little bit off topic with
the caching and storing issues in Cocoon. But I will take a look,
soon!

Cheers
Gerhard

"Sex... the pleasure is momentry, the position ridiculous,
and the expense damnable.
(Lord Chesterfield)"



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]

Reply via email to