Hi, I have taken a look into the Infinispan project, and it is interesting how much of it parallels what I am doing currently. Especially in light of my decision to use a server side hash to dispatch the remote cache requests from any server into the cluster of servers, rather than having each client maintain a connection to each server. However, at this point, it would disrupt an ongoing project to make the shift to Infinispan. That said, I expect that a lot of what I have done can be applied to the Infinispan project as well - and indeed I have joined the project dev mailing list. The current project is at a scale where significant data will be loaded into a single node, and there will be occasional writes to key/value pairs into the clustered far cache. When the write happens, the L1 (in process) cache will have to reload the altered data from the far cache. This just won't perform very well if it has to load the entire node every time. This actually seems to be working currently, except that it does reload the entire node. A slight alteration of the cache loader interceptor will load only the single effected key/value pair on a get request - I think I'll call it an L2 loader to avoid confusion with the current loader. It really will be a small, easy change, and won't be required to use the rest of the code. Thanks, Alex View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4241881#... Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&a...