2009/7/27 Dariusz £uksza <dariusz.luksza@gmail.com>
On Mon, Jul 27, 2009 at 4:18 PM, Reinhard Pötz<reinhard@apache.org> wrote:
> Dariusz £uksza wrote:
>> 2009/7/24 Dariusz £uksza <dariusz.luksza@gmail.com>:
>>>> Thanks for that tip I'll look on this ASAP ;)
>>> For our needs every pipeline should have an id parameter, from one
>>> hand it is very good solution because we get simple way how to divide
>>> and present cache entry's on JMX and on the other hand I'm not quite
>>> sure that we can require that parameter for every pipeline and user even if he
>>> don't use monitoring module
>>> What do you think ?
>> There is also third solution ... pipeline id parameter can be optional
>> and we'll publish on JMX _only_ that cache entry's that belongs to
>> pipeline that have set id parameter. This approach gives us additional
>> configuration options and can reduce amount of data published on JMX.
>> IMHO this is the best solution right now.
> +1

And here it is:

What operation (besides: getValue() and getSize()), would be useful
for every cache entry ?

getCacheKey() (mostly to print it for debugging).