"sdanig" wrote : 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. |
I have added a JIRA task to provide invalidate() across a cluster: http://jira.jboss.com/jira/browse/JBCACHE-86. This may or may not be part of 1.2.1 (due within 1-2 weeks). anonymous wrote : | - Lazy replication. When invalidated/uninitialized nodes are accessed on the clients, the data is retrieved transparently from the server cache. | What do you mean ? This is provided by the CacheLoader model in JBossCache View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3865802#3865802 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3865802 ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ JBoss-Development mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-development
