[Jboss-dev-forums] [Design of JBossCache] - Re: Reactivating SharedStoreCacheLoader

[<gal...@jb...>]

Brian, you're right. Looking at the code in _setState, it seems like that:

- The persistent state actually comes from calling CacheLoader.loadEntireState() or CacheLoader.loadState(). So the origing of the persistent state is the CacheLoader.

- The transient(in-memory) state comes from marshalling the transient state (or marshall the associated state for PojoCache) generated inside the StateTransferGenerators.

Therefore, we can control the in-memory state but we are can't really control the persistent state (with the current rules).  

In my opinion, rather than making both states consistent, the CacheLoader should be able to generate a persistent state given the in-memory state. However, in order for this to work, the structure of the in-memory state would need to be made public so that potential CacheLoader implementors could transform it into the persistent state that we're after.

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3954901#3954901

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3954901