Daniel Feist wrote:
> To "just eat the event":
>
> - You would need to be able to detect (at startup? in runtime?) that
> this will happen and then put something in place to eat it.
InMemoryCookieMonsterReceiver? :)
> - You would not be taking into account the receiver()/request() usage.
> Because even though there is no consumer/receiver configured a
> receive()/request() could be performed at anytime programatically via
> MuleClient or other, and if you have already eaten the event, the client
> code isn't going to get anything.
That is actually a good point..you can look at the
IdempotentInMemoryMessageIdStore for how to write a concurrent expiring
store that has fixed upper bounds.
Of course the other, easier alternative would be to just use a JavaSpace
and get over it. :-D
/me hums a happy tune
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
