Hi Sebastien,
First, check-out a new HEAD version and you will see
your StatusPage working proper. Just klick
on "C2 Docs" to get some items in the cache.

Second, how about a distinction between cache items
in memory and those on the filesystem.
(Hint: filesystem items are starting with cache-dir\....)

Cheers
Gerhard

"Whose cruel idea was it for the word "lisp" to have an "s" in it?"

>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.
>
>
>> >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.
>
>
>--
>Sébastien Koechlin - IVision - [EMAIL PROTECTED]
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: [EMAIL PROTECTED]
>For additional commands, email: [EMAIL PROTECTED]
>
>



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

Reply via email to