So This leads me to think that TWSocket is not
closing/freeing/de-allocating
the LocalPort, such that when I try to reopen the connection a few seconds
after I close it, windows raises the 10048 error due to the LocalPort
still
being allocated
Is this the case ????
No, it isn't. But Windows TCP/IP stack does that.
Try setting ReuseAddr property to true.
Is there something else I need to call ??
Why would you assign LocalPort ?
As I said in previous message, DO NOT ASSIGN LocalPort property. To connect
to a remote host, only the (remote) Port is important.
--
francois.pie...@overbyte.be
The author of the freeware multi-tier middleware MidWare
The author of the freeware Internet Component Suite (ICS)
http://www.overbyte.be
--
To unsubscribe or change your settings for TWSocket mailing list
please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket
Visit our website at http://www.overbyte.be
