Re: [infinispan-dev] Passivation and BCHM WAS: fixing eviction with transactions (critical for Hibernate Search)
> 2) with async stores, the issue is back. The value is not going to be
> found while it's "in flight" in the async storage queue; so unless you
> want to avoid supporting it for now, the actual removal from the
> container should be performed from the async cache loader code.
Ugh - yes, I agree. But I hate the way the mixing of concerns is starting to look. :-(
Why is this a concern when it comes to async? Async is about trading consistency for
performance, so shouldn't users expect data not to be consistent all the time?