> Many thanks, today I managed to raise an exception in 
> CommandPASV(), "port in use". The port table reported the port as 
> free, although
> the server actually was listening on that port. I was clicking
> around in multiple FTP clients when that happened.

The port release code is called from a lot of places in different
circumstances, not really look at it. 

But at least the change to use sequential ports means such in-use errors
will be much rarer, it is the normal windows behaviour to use sequential
ports, not the same one repeatedly. 

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

Reply via email to