🚀 go-pugleaf

"Robert G. Hoover" <not.a.real.address@anywhere.sorry> wrote in message
news:4129eac9@newsgroups.borland.com...

> How can I create a non-blocking socket with windows sockets?
> I've been crawling thought the documentation but haven't found
> a place to specify the non-blocking vs thread-blocking which
> corresponds to TServerSocket:::ServerType.

Use ioctlsocket() with the FIONBIO option.

> So, when I call accept, my thread is suspended, waiting for a
> client to connect. If no client tries to connect, then when I exit
> the program, the thread is still active.

Do the listening in its own thread, and then having the thread that wants to
exit the program just close the server socket directly.  The blocked
accept() in the listening thread will exit with an error and the listening
thread can then terminate in a timely fashion.

> If I can set my socket to non-blocking, then accept() will return
> an error is no client is trying to connect and my thread will be
> allowed to loop/exit, right?

You could always call select() before calling accept().  You can specify a
timeout value for select(), and select() will tell you if a client is
waiting on a listening socket or not, thus you can call accept() only when a
client is actually trying to connect and thus accept() will not block at
all.


Gambit