🚀 go-pugleaf

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

> Now my problem is this: If I try and disconnect the socket from the
> server side I can't get the socket to close because the clients try and
> connect causing the server socket to start another thread.

Only if the server is still listening for connections.  If you are closing
the server itself, it will stop listening, thus no more clients can connect.

> So I put in a flag to tell the server socket to not create the thread, but
> this does not help as the server socket still creates a connection.

If you do not want clients to connect, but you do not want to close the
server itself, then use the OnAccept event to close new connections
immediately.

> So I tried to close the ServerSocket itself and then close the active
> threads but when I do this the ServerSocket reports there are no
> active connections.

You don't need to close the threads yourself.  The ServerSocket does that
automatically.

> Anyway I am totally confused on how to properly close the Server Socket

Just close it.  You don't need to do anything else.  Everything is handled
for you.

> Now the thread does get closed but by the time I have tried to
> close all the sockets more threads more have started.

It does not matter.  They will still get closed anyway.  Do not close them
yourself at all.


Gambit