My vote is for A. Since we already have SKIP_REMOTE_LOOKUP, with a new SKIP_CACHE_LOAD as
well users will have fine-grained control. C could be added as well, but that would just
be syntactic sugar.
On 14 Oct 2010, at 11:59, 이희승 (Trustin Lee) wrote:
Galder Zamarreño wrote:
>> What about adding a unreliable_Return_Values flag? This would skip both remote
lookup and cache store (when possible).
>
> That's the key question, do we need either:
>
> a) Only a SKIP_CACHE_LOAD flag like the one suggested in
http://lists.jboss.org/pipermail/infinispan-dev/2010-October/006436.html
>
> b) A wider scope UNRELIABLE_RETURN_VALUES that encompasses both SKIP_CACHE_LOAD
functionality and existing SKIP_REMOTE_LOOKUP, keeping SKIP_REMOTE_LOOKUP.
>
> c) We have all 3 flags: UNRELIABLE_RETURN_VALUES (= SCL + SRL), SKIP_CACHE_LOAD and
SKIP_REMOTE_LOOKUP
>
> Thoughts?
C sounds best to me.
--
Trustin Lee -
http://gleamynode.net/
_______________________________________________
infinispan-dev mailing list
infinispan-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/infinispan-dev
--
Manik Surtani
manik(a)jboss.org
Lead, Infinispan
Lead, JBoss Cache
http://www.infinispan.org
http://www.jbosscache.org