[
http://jira.jboss.com/jira/browse/JBCACHE-471?page=comments#action_12362839 ]
Galder Zamarreno commented on JBCACHE-471:
------------------------------------------
Yeah, you are right.
What I was trying to say is that, imo both tasks fall under the
same umbrella, which how to resolve conflicts. Whether one
rollbacks the transaction or the other one does something more
sophisticated as merging, is just part of the resolution to the
conflict itself.
It'd be nice to provide a common structure for both.
Thoughts?
Handle JGroups MERGE
--------------------
Key: JBCACHE-471
URL:
http://jira.jboss.com/jira/browse/JBCACHE-471
Project: JBoss Cache
Issue Type: Task
Security Level: Public(Everyone can see)
Affects Versions: 1.2.4
Reporter: Manik Surtani
Assigned To: Manik Surtani
Fix For: 2.1.0.GA
When JGroups needs to do a merge due to a temporary break in the group structure, JGroups
does not handle the merging of data. This is usually left up to the application to
handle.
JBossCache should support pluggable merge policies, we could provide some simple merge
policies and allow users to write their own.
1. Evict on merge policy - when a merge occurs, evict the entire in-memory state.
Useful for Hibernate or when used with a shared cache loader.
2. Other merge algos ... ?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira