[infinispan-dev] L1 Data Container

[ben.cotton]

/> This would only affect the Cache internals (use two DataContainers instead
of one). Users still won't have direct access to the L1 cache.
/

This comment prompts me to ask the Infinispan DEV team if they believe the
following potential user API additions have merit:

Given that a user's  DIST_SYNC Cache can register a Listener to process a 

*CacheNotifier.notifyCacheEntryVisitedEvent()*

callback,

1.  provide an API enhancement so the user's  Listener can identify the
specific node at which the Visit occurred.

2. provide an API enhancement so the user's Listener can identify if the
Visit occurred at the L1 near cache.

I'm just thinking that it would be nice if a user could see a /just few
more/ exact details of how his/her

*V = cache.get(K);*

invokes distribute as "hits" on their DIST_SYNC Cache's  grid.

Thanks,
Ben






--
View this message in context: http://infinispan-developer-list.980875.n3.nabble.com/infinispan-dev-L1-Data-Container-tp4027447p4027632.html
Sent from the Infinispan Developer List mailing list archive at Nabble.com.