tetsuo3030
Programmer
I have a Window's client process that is connecting to a Window's server process. When testing a "Hard Abort" of the connection while the client is connected to the server(i.e. pulling the Ethernet cord out of my laptop, which is the client, while the status of the connection is 7 or Connected) I notice that the server does not drop the connection.. The client side drops the connection and everything "dies" as it should but the server process continues to hold on to the connection. Is it the server process's responsibility(at the Application level) to check to see if the client is still at the other end of connection and close the connection if the client is no longer there? Is there some sort of TCP/IP setting here that will make the connection time out sooner from the server side? Is there some sort of property I can specify when initiating the connection that will cause the server to check to see if the client is still "listening"? The client process is written in Foxpro and the server process is not..if that matters.
