RequestResponse with multiple RequestResponse.Clients

Jul 2, 2013 at 10:29 PM
Edited Jul 2, 2013 at 10:30 PM
Please forgive me, this is my first time trying service bus in general.

I took your RequestResponse sample and added RequestResponse.Client2. I then fire up:

RequestResponse.Server
RequestResponse.Client
RequestResponse.Client2

When I hit enter in Client2, Client receives the message. I have unique bus.OutgoingCorrelationIds, so I must be missing something.

Thanks!

P.S. What I'm trying to emulate is this. Our customer facing website will use Shuttle to Request/Respond commands. So, picture one website servicing a 1,000 users simultaneously.
Coordinator
Jul 3, 2013 at 6:14 AM
Hi Marc,

Ask as many questions as you need to :)

Each endpoint, whether playing a client or server role, probably has an inbox (I use 'probably' because it is optional). When an endpoint has an inbox (input queue) it needs its own queue. Quite possibly you have both Client and Client2 using the same queue.

Remember that a service bus is an asynchronous affair. You should not use a service bus to query data. A service bus is more suited to processing commands.

Nothing wrong with subscribing to events and letting front-end clients know about the results, though.

Hope that helps.

Regards,
Eben