Spent the flight thinking about this. As I worked through a couple of flows I realized that an incremental sequenceId will not help. Responses (confirmed/failed) to requests will take different times to process depending on the path and other such issues. Looks like a correlationId is the best we can do. John. On 2011-07-19, at 12:26 PM, John MacAuley wrote:
Peoples,
This weekend we had a lively discussion on transactionId. In the end it was agreed that we would continue to support this identifier, however it will be renamed. I have currently defined it as a uuid for uniqueness as is done in many implementations using a transactionId.
Now Inder asked if we could make it a sequence I'd to help with processing on the RA side. Comments?
Sent from my iPhone