Foxpro Client/Server, Simple Disconnection Problem

[tetsuo3030]

I have a Foxpro client application that makes a simple connection to a certain server process(not Fox) using the Winsock classes. My problem is that when I am communicating and test a hard disconnect, litterally pulling the Ethernet cord, the client process dies appropriately, but the server process holds the connection for a long time..I need the server to drop the connection on that port much earlier than it does(1 hr) if I abruptly lose connection.

Is the server responsible for closing that connection if the client is no longer "listening"? Is there a timeout value the client can specify when initiating the connection that will make the server close the connection more quickly if it loses the client?

Thanks.

 

[tetsuo3030]

Does nobody know? This seems a pretty generic question.

 

[mkrausnick]

...certain server process(not Fox)...
...the client process dies appropriately, but the server process holds the connection for a long time...

Since the server process is not Foxpro, this doesn't seem like a Foxpro issue. I'm not sure what forum it would be exactly, but maybe try Windows XP (forum779), Windows 2000 Pro (forum616) or Windows Server (forum931).

Mike Krausnick
Dublin, California

 

[DSummZZZ]

You may find a configurable property in your TCP/IP protocol configuration. Or, it may be configurable at the OS level, but I don't see any way to control it using the winsock class in VFP.


-Dave Summers-

Even more Fox stuff at:

http://www.davesummers.net/foxprolinks.htm

 

[Mike Lewis]

The server might well have a timeout property, but since we don't know what server it is, it's difficult to give any specific advice.

Mike


__________________________________
Mike Lewis (Edinburgh, Scotland)

My sites:
Visual FoxPro (www.ml-consult.demon.co.uk)
Crystal Reports (www.ml-crystal.com)