On May 2, 2013, at 7:01 PM, Pedro Ruivo <pedro(a)infinispan.org> wrote:
>> When recovery is enabled, the recovery manager creates a
second cache.
>> Someone may want to replace the Clock/TimeService for the "normal"
cache
>> and left the default implementation in the "recovery" cache.
>
> ^ Why would an end-user want to replace the Clock/TimeService?
>
> Remember what I said in my previous email: I can see someone changing the service
implementation for testing reasons, and in that case, a global clock/timer service
that's swapable via system property would work just fine IMO.
I don't know. I'm being pessimist and assuming that someone in the world
as a dark use case and needs to replace the service.
^ We already have quite a big configuration… we should think twice about adding more
stuff… :)
Cheers,
--
Galder Zamarreño
galder(a)redhat.com
twitter.com/galderz
Project Lead, Escalante
http://escalante.io
Engineer, Infinispan
http://infinispan.org