Re: [infinispan-dev] strictly not returning expired values

Not because of the cost of reading the clock, my main motivation is that we artificially create cache misses which might be very expensive to the client code. On top of that, the fact that this check also has a cost - not arguing how low - makes me wonder even more. As I see it, it's unavoidable for a cache to provide a cache miss when the data is gone, like GC'd, and we're not able to return it. It's also reasonable to expire values and remove them to make sure we don't run out of memory - but if there's a chance in which the value was not garbage collected and we're able to return it, we should return it.