Struggling with concepts

[Magnus Toftdal Lund]

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?

[Jason Meckley]

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).

[Magnus Toftdal Lund]

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)?

[Jason Meckley]

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).

[Magnus Toftdal Lund]

Thanks - that cleared some issues up.