/> William-Burns-3 wrote:
[...] My initial thought is that it would always use the same
interface,
but we could add a specific implementation later if we found additional
optimizations./
/> Daniel Berendei wrote:
[...] Users still won't have direct access to the L1 cache./
Given that you guys have started a conversation about improving ISPN's
core L1 capabilities:
The current user API for L1ConfigurationBuilder could use one more
additional capability ... i.e. it should consider providing an API mechanism
to empower the L1 end user with the capability to better determine "where he
wants to be" on the get(K) probability of "hit@L1" vs. get(K) probability
of "readThrough@remoteContainer" distribution curve (aka Pareto's weighted
expectation probability distribution. see
https://community.jboss.org/servlet/JiveServlet/download/823889-95415/Par...
).
Just an FYI (no urgency to address in an actual ISPN build), this would be
an exceptionally cool L1 user-config-API capability to provide.
--
View this message in context:
http://infinispan-developer-list.980875.n3.nabble.com/infinispan-dev-L1-D...
Sent from the Infinispan Developer List mailing list archive at
Nabble.com.