each instance would have it's own queue. you wouldn't share queues between 
instances. then for each instance you need to tell it where to send 
messages (associate the message with the endpoint).

On Wednesday, March 28, 2012 10:22:08 AM UTC-4, Magnus Toftdal Lund wrote:
>
> Thank you, but I fail to understand, whether one of the instances must 
> 'own' a given queue in order to have it processed (ie. it is listed in 
> the bus-section in app/web.config)? 
>
> On 27 Mar., 14:00, Jason Meckley <[email protected]> wrote: 
> > the distribution of work is logical, not physical. You could deploy 
> > multiple instances, interacting with one another, on a single box. or 
> you 
> > could have one instance handle all message types (although that wouldn't 
> be 
> > very efficient). 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > On Tuesday, March 27, 2012 6:24:35 AM UTC-4, Magnus Toftdal Lund wrote: 
> > 
> > > I'm a newbie when it comes to queuing concepts - so please bear with 
> me: 
> > 
> > > As I understand it, Rhino ServiceBus needs a backend 'server' - some 
> code 
> > > that handles the msmq-queue and subscriptions to it. 
> > 
> > > When I send a message to the queue, the backend should process this 
> > > message and send a new type of message to all listeners to the queue. 
> > 
> > > For my setup, I'll have two types of message - a messageType and a 
> > > replyType. A [number of] webserver[s] will use a IOnewayBus - send 
> > > messages of type messageType to the backend, which in turn consumes 
> this 
> > > message and notifies other clients with a message of type replyType. 
> > 
> > > Is my understanding correct - or can I somehow publish from the 
> > > webservers, so I don't need the backend?

-- 
You received this message because you are subscribed to the Google Groups 
"Rhino Tools Dev" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/rhino-tools-dev/-/7a1G20YJ_jcJ.
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.

Reply via email to