[ https://issues.oasis-open.org/browse/OSLCCORE-93?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=67512#comment-67512 ]
ian green commented on OSLCCORE-93:
-----------------------------------
I agree with Nick.
An adapter from TRS changelog to messages would have to consume the changelog events in (reverse) TRS order anyway, and so the adapter could be assign a sequence number, if one were not provided already in the TRS.
Defining the meaning of trs:sequence seems reasonable but it would be OPTIONAL.
> Enforce consecutive order of the trs:order numbers
> --------------------------------------------------
>
> Key: OSLCCORE-93
> URL: https://issues.oasis-open.org/browse/OSLCCORE-93
> Project: OASIS OSLC Lifecycle Integration Core (OSLC Core) TC
> Issue Type: Bug
> Reporter: Andrii Berezovskyi
> Labels: TRS
>
> If TRS events are to be distributed via messaging systems without strict ordering guarantees (eg partitioned Kafka topics), a Resequencer EIP pattern might need to be applied. The pattern requires the message order ids to be sequential in order to unambiguously define whether there are any out-of-order messages still missing from the internal resequencing buffer.
> I think a single atomic counter is not too much to ask from the TRS server implementers.
> http://www.enterpriseintegrationpatterns.com/patterns/messaging/Resequencer.html
--
This message was sent by Atlassian JIRA
(v6.2.2#6258)
