🚀 go-pugleaf

"Pere Mateu" <pmateu@siam.es> wrote in message 
news:476a39a8@newsgroups.borland.com...

> I'm working in blocking mode

The Connected property is not accurate in blocking mode, because there is 
nothing to reset it when needed.  You have to use a TWinSocketStream to 
read/write data, and TWinSocketStream does not make updates to 
TClientSocket's properties.  So you have to look at the return values of 
your actual reading/writing operations instead.

When reading, if TWinSocketStream::WaitForData() returns true and then 
TWinSocketStream::Read() returns 0, the connection was disconnected 
gracefully.  If the socket was disconnected abnormally, however, then 
WaitForData() will never return true, so you have to watch out for that. 
TWinSocketStream.Read() will throw an exception if it couldn't read from the 
socket.

When writing, there is no waiting.  If TWinSocketStream.Write() returns 0, 
the socket was disconnected gracefully.  If there is an error writing to the 
socket, an exception is thrown.

> I guess I'll have to use these socket functions, because there's
> nothing I can use in the stream.

Yes, there is.  See above.


Gambit