I have this situation:
1) There is a server on machine S which exposes type T through .NET remoting.
2) There is a client on another machine C which attempts to remotely instantiate the type T on machine S using Activator.GetObject method.
If the S machine is running but the server application (which exposes type T) isn't running, you will get an System.Net.Sockets.SocketException with ErrorCode set to 10061 meaning "No connection could be made because the target machine actively refused it."
If the S machine itself is NOT running you will get an System.Net.Sockets.SocketException with ErrorCode set to 10060 meaning "A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.", but after an unreasonable (in my opinion) long timeout.
How can I control this timeout? (Within the client applications, of course )
10x.
1) There is a server on machine S which exposes type T through .NET remoting.
2) There is a client on another machine C which attempts to remotely instantiate the type T on machine S using Activator.GetObject method.
If the S machine is running but the server application (which exposes type T) isn't running, you will get an System.Net.Sockets.SocketException with ErrorCode set to 10061 meaning "No connection could be made because the target machine actively refused it."
If the S machine itself is NOT running you will get an System.Net.Sockets.SocketException with ErrorCode set to 10060 meaning "A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.", but after an unreasonable (in my opinion) long timeout.
How can I control this timeout? (Within the client applications, of course )
10x.