On Jul 13, 2005, at 4:30 PM, Doug Franklin wrote:
For instance, we've found that when our Windows code calls
closesocket() on a SOCK_STREAM socket (but not on a SOCK_DGRAM
socket),
wineserver refuses to actually close and release the socket for
several
minutes, so if you stop our app, you can't start it for several
minutes, or its bind() or listen() call will fail because the
socket we
closed still exists and still owns the port.
What state is the socket in? I remember having issues with the
TIME_WAIT state when closing a socket in a small application I wrote
a couple of years ago. Unfortunately I can't help beyond that
because I ended up replacing the socket code with a second named
pipe, which was much better suited to what I was doing.
Cheers,
- Dave
http://www.digistar.com/~dmann/
