[jboss-jira] [JBoss JIRA] Commented: (JBCACHE-471) Handle JGroups MERGE

Tue May 22 03:28:52 EDT 2007

    [ http://jira.jboss.com/jira/browse/JBCACHE-471?page=comments#action_12362822 ] 

Manik Surtani commented on JBCACHE-471:
---------------------------------------

Somehow for optimistic workspace merging I think the correct approach should be a tx rollback since each workspace is a clearly defined and identifiable unit of work.  

In the case of a JGroups merge, both pieces may contain multiple unidentifiable transactions which cannot be rolled back or resolved, and hence the need for a merge.

> 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