Crowley, Yes, that is the general idea. In general, an endpoint (a bus instance) is something that run in its own AppDomain. I intentionally didn't give any options to handle that at a lower granularity, because an endpoint should be only about one thing.
On Wed, Jan 6, 2010 at 6:17 PM, crowley_mark <crowley_m...@yahoo.com> wrote: > Further testing reveals that if each consumer is hosted in a separate > process setting the threadcount of the bus to one for the long running > process will suffice. > > Its only if there are multiple consumers in the same process that in > the above example the sending of email would be delayed by the long > running process if threadcount=1, or multiple instances of the long > running porcess would be in operation if threadcount > 1. > > For my scenario the long running porcess will be on a separate process > on a separate machine, so all is good in the world. > > Nice work on this by the way, very smart solution! > > -- > 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<rhino-tools-dev%2bunsubscr...@googlegroups.com> > . > 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 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.
