Check the mailing list, it was posted there. On Wed, Mar 24, 2010 at 2:01 AM, Jan Limpens <[email protected]> wrote:
> NH Saga Storage? How interesting! Is there anything written about that > somewhere or is it reading the sources? > > > On Tue, Mar 23, 2010 at 3:31 AM, Ayende Rahien <[email protected]> wrote: > >> Yes, you could check for the order state in the delay message. >> And checking the saga state depends on how you store it. If you use NH >> Saga Storage, that is easy, if you use Pht Saga Storage that isn't going to >> happen. >> >> >> On Tue, Mar 23, 2010 at 4:45 AM, Jan Limpens <[email protected]>wrote: >> >>> inline, too >>> >>>> >>>> >> 1/ bus.DelaySend >>>>> > >>>>> > how could I cancel this, in case the payment arrives? >>>>> I could of course, upon state change delaysend a >>>>> CheckIfIsStillInStateMessage, that would either be answered with a >>>>> AbendondedWarningMessage or nothing. Would this be the way to go? (A >>>>> bit non-obvious in my eyes) >>>>> >>>>> >>>> Not following what you are doing here >>>> >>> >>> Assume we get a new Order. We delay send a CheckIfIsStillInStateMessage >>> containing the orders' current state and id. Some time in the future the >>> message arrives at a consumer. The consumer can now check if the order is >>> still in the same state as it was, when the message was created and >>> accordingly send a AbandondedWarningMessage if that`s the case. >>> >>>> >>>> >>>> >>>>> But this would somewhat transgress the borders between domain and >>>>> services, wouldn't it? >>>>> >>>> >>>> No. Saga is for maintaining state over multiple messages easily. >>>> Otherwise you have to roll your own state maintainence. >>>> >>> >>> How would I be able to get an order's state (or many orders' states)? For >>> example to display a page-able list of orderids with their state. >>> >>> Thanks for helping me to wrap my mind around this! >>> >>> -- >>> 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]<rhino-tools-dev%[email protected]> >> . >> For more options, visit this group at >> http://groups.google.com/group/rhino-tools-dev?hl=en. >> > > > > -- > 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.
