🚀 go-pugleaf

"mike" <mfbrowne@earthlink.net> wrote in message
news:41166225$1@newsgroups.borland.com...

> what happens is shortly after the actual socket send takes
> place the socket is dropped. There is no exception or
> error that I can see, it just simply drops.

Please show your actual sending code.  Sockets don't just drop without
saying why, so there has to be an error being reported somewhere..

> So my question is, in a threaded server socket, what is the
> proper way to send a message to all connected clients.

Exactly what you are already doing - looping through the server's
connections sending to each one.  Although I have to question your use of
InfoToSendToAllClients.  What happens if a thread has not sent
InfoToSendToAllClients yet when another multi-client message comes through?
Is InfoToSendToAllClients overwritten?  Sounds like you need to implement
some kind of queing system, if you are not already doing so.


Gambit