inline, too
On Sun, Jun 6, 2010 at 11:39 PM, Corey Kaylor <[email protected]> wrote:
>
> The message will be discarded.
> What happens if a saga delay sends a message and the message is triggered
> after the saga has been completed / deleted?
>
This means it lands in the "discarded" sub queue? Is this queue emptied
somehow or does it simply accumulate?
>
> What does HandleCurrentMessageLater() actually do?
>>
> It sends the message back to itself as a deferred message for Now.
> Essentially allowing other messages if any to be processed first. I've never
> had a use for this myself.
>
So if I have this:
public void Consume(SomeMsg msg){
if (someConditionIsNotMet)
HandleCurrentMessageLater();
else
DoSomethingMeaningful(msg);
}
it would resend that message until the condition is met, right?
at which rate? will it ever give up or slow down?
>
>
>>
>> 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)
>>
>
> They are not different, other than with only ConsumerOf<> you will not have
> the State property set in your consumer class via the ISagaPersister.
>
I don't get that... once you get to executing this message handler, the saga
is already alive (and the state has been constructed).
That said, I don't quite understand the usefulness of the separate, usually
anemic state class. How is it actually different from extending the saga
directly?
--
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.
