I have a message which may participate in a saga, or it may be sent from an internal process. If it is part of a saga, then the standalone consumer shouldn't be invoked. I am not sure the simplest way to handle a rule like this...placing additional context on this message would be--difficult. The message would be handled twice if it is part of a saga right now. I thought about a message module, but that seems real heavy handed. SagaFinders are cool but don't help out. Is there any other way folks have imposed a policy on message handling?
-- You received this message because you are subscribed to the Google Groups "Rhino Tools Dev" group. To post to this group, send email to rhino-tools-...@googlegroups.com. To unsubscribe from this group, send email to rhino-tools-dev+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/rhino-tools-dev?hl=en.
