That kind of goes against the delivery guarantee if we were to drop the
connection when the IP is down. For sending out publish notifications when
you don't care about delivery others have suggested that maybe UDP is a
better option? bus.Unsubscribe might be another option.

On Thu, Mar 31, 2011 at 3:24 AM, Paul Durrant
<[email protected]>wrote:

> i have figured out what is going on,  in that the live server still
> has an item linking it to the dev client from when it was running as a
> live client, and therefor still pushes the messages  to the same IP,
> my question is therefor how can i remove the client from the server
> side list of clients as the only option is host.start, how do you
> discontect a client? or shouldn't the serverside drop the connection
> when it can no longer push to that IP?
>
> On Mar 29, 10:37 am, Paul Durrant <[email protected]> wrote:
> > i have 3 services    dev,uat and live
> >
> > in my dev instance the client is still receiving messages from the
> > live service even though i have change the  config
> > to
> >
> >      <add assembly="messages" name="Messages" endpoint="rhino.queues://
> > localhost:50001/Position_Backend" />
> >
> > from
> >
> >      <add assembly="messages" name="Messages" endpoint="rhino.queues://
> > Messagebus.domain.com:50001/Position_Backend" />
> >
> > how can the client still be  listening to the live service ?
>
> --
> 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.
>
>

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