question

Upvotes
Accepted
61 2 4 9

Ordering of CacheControl Messages

In the Redi API when getting messages via the CacheControl how can I determine the order that messages were received? For example I place an order into the demo environment and receive two messages back. The first message response has a RediOrderRefKey of SYBxxxxx and the second message has a RediOrderRefKey of YS61222xxxxx. I know that the SYB is the stand in message for a new order and the YS6 is for the real accepted order. But not having that knowledge I can't find a field in the CacheControl message that puts these updates in any particular order. I thought the Time field might update with each message but my testing shows that the time value remains the same whether I receive a message about a new order or a second message, a few minutes later, about that same order being cancelled.

Is there an enumerator that will tell me the correct order?

Should I just assume that order cache events will show up in the correct order and I can just increment my own internal counter?

redi-api
icon clock
10 |1500

Up to 2 attachments (including images) can be used with a maximum of 5.0 MiB each and 10.0 MiB total.

Upvotes
Accepted
21 0 0 0

@tobermarkCache control is guaranteed to fire events in the correct order.

icon clock
10 |1500

Up to 2 attachments (including images) can be used with a maximum of 5.0 MiB each and 10.0 MiB total.

Upvotes
21 0 0 0

Cache Control is guaranteed to fire events in the correct order.

icon clock
10 |1500

Up to 2 attachments (including images) can be used with a maximum of 5.0 MiB each and 10.0 MiB total.

Click below to post an Idea Post Idea