🚀 go-pugleaf

"newsgroups.borland.com" <lapoguidi@alice.it> wrote in message 
news:4724bebc@newsgroups.borland.com...

> I have a TServerSocket in non-blocking listening on port 5678.

Is the client running in blocking or non-blocking mode?

> It seems to work fine for some time, then the error 10053 appears.

On which side?  The client or the server?

> What I'm doing wrong?

You are not using the return value of SendBuf() on the server side, or the 
return value of ReceiveBuf() on the client side.

The server is non-blocking, so you need to use its OnWrite event when 
blocking transmissions occur.  When SendBuf() returns -1 without raising an 
exception or generating an OnError event, you have to buffer the data you 
were trying to send at the time and then re-send it when the OnWrite event 
is triggered at a later time.  You have to do that on a per-connection 
basic, so I suggest you make use of TCustomWinSocket's Data property for 
that.  One thing you could do is store a TMemoryStream object in that 
property, and then cache the data when needed.  Please go to 
http://www.deja.com and search through the newsgroup archives.  I've posted 
examples of this several times before.

You are also not checking the return value of ReceiveLength() on the client 
side for values less than 1.  If your client is running in non-blocking 
mode, then multiple packets can trigger multiple OnRead events.  However, 
your reading in the first event may receive all of the available data from 
both events, leaving nothing for the second event to read.  So you need to 
account for that possibility.

Alternatively, you might consider switching to a UDP-based protocol, such as 
MultiCasting or RTP, instead of trying to use TCP for real-time 
broadcasting.  TCP is not really designed for that.


Gambit