I just finished two major pieces of work to make this consistent.a) we always receive a message before processing it. b) when we move a message (which require a peek), we send it to the queue again and move it from there in a peek, that is an atomic operation c) processing message is done using the sync MSMQ API, vs. the async one, which has proven itself bugy
On Sun, Jan 25, 2009 at 1:06 AM, Ayende Rahien <[email protected]> wrote: > The threading model for the bus is done by spawning multiple Begin Peek > calls. > That is causing a problem because when a message arrives, we get notified > for the _same_ message on all threads. > I am not sure how to resolve this issue. > Any ideas? > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
