+1
Dan
On Mon, Sep 7, 2015 at 2:52 PM, Galder Zamarreno <galder(a)redhat.com> wrote:
> Makes sense.
>
> --
> Galder Zamarreño
> Infinispan, Red Hat
>
> ----- Original Message -----
>> A recent issue with some refactoring of the PassivationInterceptor
>> affecting code using it directly (EAP's Infinispan subsystem), has got
>> me thinking about the fact that we have somewhat treated interceptors as
>> a form of API since we do not provide another way of retrieving metrics
>> collected by the interceptors, aside from the basic cache stats.
>> With the plan to eventually drop interceptors, these kind of metrics
>> should be exposed through a more stable API (aside from maintaining
>> stability of the MBean side of things).
>>
>> The org.infinispan.stats.Stats interface already partially covers that
>> for basic stats (see org.infinispan.cache.AdvancedCache.getStats()), and
>> I think it should be extended or at least complemented to do this.
>>
>> WDYT ?
>>
>> Tristan
>> --
>> Tristan Tarrant
>> Infinispan Lead
>> JBoss, a division of Red Hat
>> _______________________________________________
>> infinispan-dev mailing list
>> infinispan-dev(a)lists.jboss.org
>>
https://lists.jboss.org/mailman/listinfo/infinispan-dev
>>
>
> _______________________________________________
> infinispan-dev mailing list
> infinispan-dev(a)lists.jboss.org
>
https://lists.jboss.org/mailman/listinfo/infinispan-dev
_______________________________________________
infinispan-dev mailing list
infinispan-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/infinispan-dev