> > Your code does not guarantee that all data will be sent
> > to the client. Make sure that ShutDown() is called after
> > all data has been delivered to winsock. Something like
> > that:

> Thanks Arno.  But now I'm confused:  It was because I was told to call
> Shutdown(1) that I used it when closing the connection.  I was told on
> this list that that's what I should do to ensure that the closing
> message data is delivered before closing the connection.  Was this not
> accurate?

Shutdown call winsock API but TWSocket has an internal buffer for data to
send. Winsock will gracefully close the connection considering only data it
already has. And actually TWSocket.Shutdown directly call the API without
worrying about buffered data to be sent.

Contribute to the SSL Effort. Visit http://www.overbyte.be/eng/ssl.html
--
[EMAIL PROTECTED]
Author of ICS (Internet Component Suite, freeware)
Author of MidWare (Multi-tier framework, freeware)
http://www.overbyte.be

-- 
To unsubscribe or change your settings for TWSocket mailing list
please goto http://www.elists.org/mailman/listinfo/twsocket
Visit our website at http://www.overbyte.be

Reply via email to