Hi, We are currently developing a client/server application. The server uses Hibernate for persistence, with TreeCache for the second-level cache. The clients need local data caches, and we were thinking that an easy way of implementing these local client caches might be to replicate the server cache to all the clients.
However, we are hesitant to go this route due to the amount of data that could be involved. There are two cache features that would make the outlined implementation more palatable: - An invalidation model. When a node gets updated on the server, the clients receive notification that the specified node is no longer valid, but do not retrieve the data itself. - Lazy replication. When invalidated/uninitialized nodes are accessed on the clients, the data is retrieved transparently from the server cache. I have searched the forums and have found a couple of similar questions, some suggesting the use of a custom CacheLoader, or perhaps SharedStoreCacheLoader or DelegatingCacheLoader. However, neither of these can be configured via XML (no empty constructor), and even configuring them via code, it's not clear whether or not you can specify remote CacheLoader's/TreeCache's to delegate to. I'd be interested to hear what people think our options might be. Aside from switching to OSCache ;-) Regards, Daniel Gredler View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3865588#3865588 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3865588 ------------------------------------------------------- This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting Tool for open source databases. Create drag-&-drop reports. Save time by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. Download a FREE copy at http://www.intelliview.com/go/osdn_nl _______________________________________________ JBoss-Development mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-development
