Folks,
I'm a total noob with RSB, so I'll apologize in advance if this is a
dip-stick question. But here goes:
I inherited a system that has a Windows service that contains an RSB
instance. The Windows service exposes a web service which some
external entities use to interact with RSB indirectly. That much I can
follow OK. :-)
The same server runs IIS and has an ASP .NET-based web site that has
its own copy of the RSB DLLs. The RSB configuration is identical to
that of the Windows service (config is appended). This is the part
that scrambles my brain... how do two RSB instances in different
processes accessing the same message queues keep from clobbering each
other? Does RSB just have the dark magic that keeps it all straight?
It seems to work, I have to admit. The messages from the ASP .NET
application are indeed making their way down to the Windows service
code.
But is this a normal way to architect a distributed system with RSB,
particularly for communication between ASP .NET and a Windows service
with RSB? There's a part of me that just wants One RSB to Rule Them
All. :-)
Thanks... == Ross-a-roni ==
<castle>
<facilities>
<facility id="payment.service">
<!-- bus is the name of the local bus queue endpoint -->
<bus name="payment.service" threadCount="1" numberOfRetries="5"
endpoint="msmq://localhost/paymentProcessor"/>
<messages>
<!-- add a line for every namespace containing events that we
want to subscribe to -->
<add name="DP.Payment.Messages" endpoint="msmq://localhost/
paymentProcessor" />
</messages>
</facility>
<facility id="payment.client">
<!-- bus is the name of the local bus queue endpoint -->
<bus name="payment.client" threadCount="1" numberOfRetries="5"
endpoint="msmq://localhost/paymentClient"/>
<messages>
<!-- add a line for every namespace containing events that we
want to subscribe to -->
<add name="DP.Payment.Messages" endpoint="msmq://localhost/
paymentProcessor" />
</messages>
</facility>
</facilities>
</castle>
--
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.
