[
https://issues.apache.org/jira/browse/JUDDI-915?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14297392#comment-14297392
]
Alex O'Ree commented on JUDDI-915:
----------------------------------
the spec offers a newDataConditional, in which someone saves something, then
checks with everyone else to see if that key isn't already in use. upon
negative acknowledgment, then the something is saved and committed.
> investigate replication conflict handling
> -----------------------------------------
>
> Key: JUDDI-915
> URL: https://issues.apache.org/jira/browse/JUDDI-915
> Project: jUDDI
> Issue Type: Task
> Components: core
> Reporter: Alex O'Ree
> Assignee: Alex O'Ree
> Fix For: 3.3
>
>
> there's a few scenarios in which data can be conflicted in replication
> -identify what the spec says about them
> related to custody transfer and replication
> if an identify entity is created at two different nodes (tmodel keygen) at
> the same time, then it should be conflicted due to node ownership. then try
> modifying one of them and confirm that the other is not changed and that
> custody is not transfer inadvertently.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
