🚀 go-pugleaf

"Joel Guerra" <j.guerra@texasscenic.com> wrote in message
news:42665b58@newsgroups.borland.com...

> Thanks, this works most of the time, but I still have a
> problems every now and again if I pull the enet cable out.

Under most versions of Windows, the socket stack cannot detect that to begin
with, so sockets have no way of knowing that they are actually gone.  This
is actually by design.  Temporary outages on a LAN/WAN are common.  Socket
stacks are designed to handle that situation internally by keeping sockets
"alive" for an period of time.  If the network comes back in a timely
fashion, the socket stack can reestablish communication with the remote
machine silently and gracefully, and the application will never know that
the connection was ever down.  If the network does not come back, or if the
remote machine cannot be reached anymore, then the stack still has no way of
knowing that the socket connection is really gone until the socket times out
internally.  Only then can the socket be invalidated by the socket stack.
Until that happens, the socket stack does not report any errors on the
socket, so the application has no way of knowing what.is happening.


Gambit