As the NServiceBus documentation mentions here http://www.nservicebus.com/Distributor.aspx in the "What about MSMQ v4?" section, remote transactional receives are also a scalability bottleneck that you might want to weigh as you decide which design approach to pursue.
Steve Bohlen [email protected] http://blog.unhandled-exceptions.com http://twitter.com/sbohlen On Fri, Jun 11, 2010 at 9:51 AM, Corey Kaylor <[email protected]> wrote: > Interesting, it looks like they did add support in 4.0 for remote > transactional receives. Does this mean it should be a recommended thing? Or > is the recommended usage to receive from a local queue, and send to remote > queues? I guess it's specific to the needs of the application, but my gut > reaction is the latter. > > -- > 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.
