Yeah I gathered that...and prefer it too. It's been good for me
anyways to dig into the appropriate approach to asynch ops anyways. I
am still working on a demo mr app though if you want it.

I did see in the AddInstanceSubscription code in the
MsmqSubscriptionStorage that if you were to add an instance
subscription for a type which is already registered you'd actually get
the message twice in that consumer's type...once in the instance and
once in the container-created instance. This seems like the element of
least surprise (sorta) but should be well-understood.

On Dec 20, 4:53 pm, "Ayende Rahien" <[email protected]> wrote:
> I have explicitly tried not to give an answer for that. That is, I consider
> this outside the scope of RSB.
> You can handle this with instance subscriptions, but I am putting all thread
> handling semantics outside of RSB, you have to take care of that yourself.
>
> On Fri, Dec 19, 2008 at 11:05 PM, Mike Nichols 
> <[email protected]>wrote:
>
>
>
> > I am trying to implement request/reply in rhino esb for MonoRail.
> > I looked at the MassTransit impl and I know they have an
> > IServiceBusRequest object for doing that.
>
> > I don't fully understand AddInstanceSubscription, even after going
> > thru the esb code and request/reply tests. WHen I do this:
> > var handler = new REsponseMessageHandler(this);
> > using (bus.AddInstanceSubscription(this.handler))
> >  {
> > bus.Send(new RequestMessage(someText));
> > }
>
> > Should the bus.Reply() call inside my REquestMessageHandler consume
> > the passed in instance of 'handler'? It keeps resolving through the
> > container so any state I have is lost.
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to