Re: Detecting a dead proxy to a remote object
- From: "Goran Sliskovic" <gsliskov@xxxxxxxxx>
- Date: Tue, 6 Dec 2005 13:09:14 +0100
"Michael Groeger" <google.news@xxxxxx> wrote in message
news:uyqqXcl%23FHA.1032@xxxxxxxxxxxxxxxxxxxxxxx
> Hi Chris,
>
> thanks but I am forced to use framework 1.0 :(
>
> Regards,
> Michael
....
You could use interop to implement ping (w2k and xp comes with
iphlpapi.lib/ICMP.dll). Check IcmpSendEcho in MSDN.
Hower, this is "poor man's" checking of service availability. Fact that ping
does not work does not mean that computer is unreachable. Also, if ping
works, that does not mean that service is reachable. NET remoting is missing
connection management and that is serious defect IMHO (plus there is no call
timeout, which is also very dangerous). You could try third party product
genuine channels that has implementation of bi-directional channels and also
connection management and guranteed call timeout. I have not tested it
though.
Regards,
Goran
.
- References:
- Detecting a dead proxy to a remote object
- From: Michael Groeger
- Re: Detecting a dead proxy to a remote object
- From: Chris Yager
- Re: Detecting a dead proxy to a remote object
- From: Michael Groeger
- Detecting a dead proxy to a remote object
- Prev by Date: Re: Detecting a dead proxy to a remote object
- Next by Date: Hosting a Remote Server on IIS, .NET 2.0
- Previous by thread: Re: Detecting a dead proxy to a remote object
- Next by thread: Re: Client IP Address
- Index(es):
Relevant Pages
|