Re: [infinispan-dev] [Discussion] TimeService implementation

preciseTime() {return (cached = System.nanoTime());} impreciseTime() {return cached;}

Also, I think a method like boolean isExpired(long timestamp) is useful >> to add to the interface. >> >>> >>>> >>>> * Scope: >>>> >>>> Should the TimeService be in a cache or global scope? My vote is per >>>> cache… >>> >>> ^ My feeling is that it should be global. Why per cache? >> >> 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. Looking at the code, it is easiest for me to use a global service :)