1/ bus.DelaySend 2/ Yes, you can save the order id in the saga state 3/ A saga is just a way to encapsulate a state machine, it is pretty common to have the current state flag in the saga state.
On Tue, Mar 16, 2010 at 1:17 AM, Jan Limpens <[email protected]> wrote: > hello, > > a few more question on how to implement things in a nice way :) > > > 1. I have an OrderSaga and I want it to send a message if n days went > by and the customer has not yet paid for the order. I suppose it is no good > idea to Thread.Sleep for n days :) > How does one implement such a thing? > Is the saga kept alive for the whole period of its non-conclusion or is > it brought to live every now and then and checked, if there is something > that needs to be done? > > 2. Should I reference the persisted Order in the Saga (via it's id)? > > 3. If the Order has an enum State of possible states, should my > OrderStates class (the one I pass to the Saga via ISaga<OrderState>) wrap > the enum and the order to conclude which the current state is? Or should I > better keep this decoupled (and duplicated) > > Sorry for spamming the list & thanks!! > > -- > 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]<rhino-tools-dev%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/rhino-tools-dev?hl=en. > -- 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.
