honestly I wouldn't use remoting for this. I would just use a DGRAM socket and send a custom UDP packet to it and wait for the response. With remoting your getting a whole lot of extra things that aren't necessarily what you want.
However, if you really need to use remoting for this, you would need to use the lifetime management calls to implement something to push clients out of memory. If they are a CAOs then it's easy as you can just track the creation in your SAO Class
factory. If they are SAO's then you might consider using a trackinghandler to track creation (so you can later use the lifetime services to close them).
On Fri, 26 Aug 2005 17:37:44 GMT, James <Kimo.Ford@Anheuser-Busch.com> wrote:
>Ok. I have been banging my head about this issue for the last couple of days. I have tried just about everything i could find out there but nothing is exactly what i am experiencing.
>
>Currently I am developing a Server Awareness program that runs on the client. The basic principle is that in the event that the Server goes down the Client will recognize this at which time it will disconnect and unregister the channel then establish a new connection to the backup server.
>
>The issue is many and i will try to list them out.
>
>1. Disconnect. That or rather I cannot seem to get that working - Will usually end up getting an error such as "Cannot disconnect from a proxy"
>2. Unregister - This part goes fine but when i try to RegisterWellKnow..... again to the secondary server I get the errror that " Cannot redirect already redirected".
>
>does anyone know of a way to do what i am asking which is to basically kill all the connections to the dead server and establish a new connection to the secondary server with out shutting down the client UI.
>
>Any help would be greatly appreciated.
>
>thanks,
>
>Jim
>
>From
http://developmentnow.com/g/24_0_0_0_0_0/dotnet-framework-remoting.htm >
>Posted via DevelopmentNow.com Groups
>
http://www.developmentnow.com
