🚀 go-pugleaf

Hey Bob. Thats pretty helpful.

I've tried the following code in the OnConnect event of the TClientSocket
though it returns 10038:

WSAAsyncSelect ((SOCKET)Socket->Handle, Handle, WM_FD_CLOSE, FD_CLOSE)


What am I doing wrong here?


--------------------------------------------------------------------------

WSAENOTSOCK
(10038)
  Socket operation on nonsocket.
  An operation was attempted on something that is not a socket. Either the
socket handle parameter did not reference a valid socket, or for select, a
member of an fd_set was not valid.


"Bob Gonder" <notbg@notmindspring.invalid> wrote in message
news:obssdvopq540mjv03irip73n9rmd9aes4k@4ax.com...
> >"Tharun Pillay" <tharun@webmail.co.za> wrote in message
> >
> >> Trouble is that we don't know when the *server* must
> >> close the connection - we are relying on a timout or the
> >> client terminating the connection - which is dodgy.
>
>
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/winsock/win
sock/shutdown_2.asp
> Also see ../closesocket_2.asp particularly about SO_DONTLINGER.  And
> the link there to "(see Graceful shutdown, linger options, and socket
> closure for more information)".
>
> To assure that all data is sent and received on a connected socket
> before it is closed, an application should use shutdown to close
> connection before calling closesocket. For example, to initiate a
> graceful disconnect:
>
> 1)Call WSAAsyncSelect to register for FD_CLOSE notification.
> 2)Call shutdown with how=SD_SEND.
> 3)When FD_CLOSE received, call recv until zero returned, or
> SOCKET_ERROR.
> 4)Call closesocket.
>
>
>