Component doesn't recognize disconnection

When I unplug the cable, the component doesn't recognize disconnection - why not?

Date Entered: 6/17/2004    Last Updated: 6/17/2004

When a connection is unexpected CUT - i.e. Ethernet cord pulled out of wall, modem unplugged, etc - it takes the OS up to several minutes to realize what has happened (and as a result, winsock does not know that the connection has been lost. Since winsock doesn't know, the component does not know either). Note that if you to send something on this connection - winsock will indeed realize that the connection has been broken and an exception will be thrown.

We appreciate your feedback.  If you have any questions, comments, or suggestions about this entry please contact our support team at kb@nsoftware.com.