🚀 go-pugleaf

Remy,

Thanks for answering, but I was being really stupid. On the receiving end of
the broadcast I was closing the socket. It was test code from long ago that
I had forgotten about. I knew it was something stupid and it did not make
sense to me at all, then I found the test code and went "DAh".

Again thanks.

Mike
"Remy Lebeau (TeamB)" <gambit47.no.spam@no.spam.yahoo.com> wrote in message
news:41169ab1$1@newsgroups.borland.com...
>
> "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
>
>