🚀 go-pugleaf

Thank you both for answering the information was most helpful.

I did consider sending a message to the clients to stop attempting to
reconnect but I was looking for another way because if the server side is
closed then it is because trouble is being experienced on the net and I just
want to shut it down and then bring it up again and let all clients connect
again.

I have also detected that a client can thing it is still connected but in
reality is not. Have no clue where the connection goes but just seems to go
quite. When this happens the server side also does not detect the loss of
the connection for whatever reason. So by sending a message to the client at
shut down it may never get there.

Anyway, I have adjusted to close the socket at the server side and it
appears to work as Remy indicated. I will get a chance next week to try it
in the real life environment to see if it works. I sure hope so.

Anyway, thanks again for the information and hopefully it all works.

Mike


"Remy Lebeau (TeamB)" <no.spam@no.spam.com> wrote in message
news:41def727$1@newsgroups.borland.com...
>
> "Bob Gonder" <notbg@notmindspring.invalid> wrote in message
> news:e8rtt0hpur3uhbmfu9aocea2u76lr1qqvd@4ax.com...
>
> > Could you have the server send a "shutdown" message to
> > the clients so they would cease trying to reconnect?
>
> I had considered mentioning that earlier, but did not.  Under ideal
> conditions, when everything is managed properly, such a packet is not
> actually needed.
>
> > Will this code actually close all connections?
>
> The connections are not removed from the list until they are physically
> freed from memory.  Whether that happens immediately or not depends on
> whether the server is being used in blocking or non-blocking mode.
>
>
> Gambit
>
>