What happens if a saga delay sends a message and the message is triggered after the saga has been completed / deleted?
In the starbucks sample, the cashier passes his correlation id to the barista. How would this be handled for multiple PrepareDrink requests stemming from a single cashier saga? Imagine the sagas were persisted in the db with the CorrelationId as primary key. Should every barista saga have it's own CorrelationId and keep a reference to it's parent cashier saga? I suppose so, but there might be a better way, as this seems to break, what correlation seems to be about. What does HandleCurrentMessageLater() actually do? Are there differences between Orchestrates<> and ConsumerOf<> (are messages being treated differently? different order, maybe? or something else?) Cashier saga seems to have used Orchestrates<> and was later changed to ConsumerOf<> (see region name vs implemented interface) Is there (should there be) a way to make a consumer be the first to handle a certain message? -- Jan -- You received this message because you are subscribed to the Google Groups "Rhino Tools Dev" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/rhino-tools-dev?hl=en.
