cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Dariusz Łuksza <dariusz.luk...@gmail.com>
Subject Re: [c3 monitoring] Cache overview
Date Fri, 17 Jul 2009 20:46:53 GMT
2009/7/17 Dariusz Łuksza <dariusz.luksza@gmail.com>:
> On Fri, Jul 17, 2009 at 5:35 PM, Simone Gianni<simoneg@apache.org> wrote:
>> Dariusz Łuksza wrote:
>>>
>>> On Fri, Jul 17, 2009 at 7:16 AM, Reinhard Pötz<reinhard@apache.org> wrote:
>>>
>>>>
>>>> Dariusz Łuksza wrote:
>>>>
>>>>>
>>>>> On Wed, Jul 15, 2009 at 8:43 PM, Simone Gianni<simoneg@apache.org>
>>>>> wrote:
>>>>>
>>>>
>>>> Just one quick comment for now (I'll get back to you with more thoughts
>>>> at the weekend but the discussions already goes into the right direction
>>>> IMHO):
>>>> Does this still work if you have thousands or tens of thousands cache
>>>> entries?
>>>>
>>>>
>>>
>>> In this case it'll cost some CPU time and user patience to find elemnt
>>> that he is actually looking for, but right now I don't have anny other
>>> ideas ...
>>>
>>>
>>
>> I was thinking the same when writing about the "burst" operations, that will
>> narrow down the list based on user input, making it possible to work on a
>> subset. IMHO there should not be a complete list service, or it should
>> report something like 100 entries and then state that there are x-thousands
>> more.
>>
>
> OK, but I see here one problem, how we perform edit action on a single
> entry ? How we can find that entry, and choose it to edition ?
>
> I mention about that, because being able to edit cache entry is one of
> feature on my goal list ;)
>

BTW. What you are thinking about implementing something like
valueSet() or cachedValueSet() for each Cache ?

I mean that we can add that method into
o.a.coccon.pipeline.caching.Cache interface, in some cases it would
make code more simlier.

-- 
Best regards

Blog: http://luksza.org
LinkedIn: http://www.linkedin.com/in/dariuszluksza

Mime
View raw message