Hello Paul, For winsock it make no difference, socket will close anyway. It is possible that you have due to the bad (inter)networking problem many sockets in TIME_WAIT state. Possible you ran out of free memory (non paged) witch is recovered after reboot. I dont think you can recover it yourself.
But if it is TIM_WAIT then you can short the time somewhere in registery. Use netstat -a to check out. --- Rgds, Wilfried [TeamICS] http://www.overbyte.be/eng/overbyte/teamics.html http://www.mestdagh.biz Friday, May 5, 2006, 21:59, Paul wrote: > Hi, > the last couple of days, I've had a very bad internet connection (http). > Our provider is upgrading the network to double the speed. > I found that when a connection failed (time-out , error) the errors kept on > comming, even after restarting the program. > After rebooting the computer, it worked better again for a while. > So I assume this is a winsock problem. > Can it be reset by code ? > What is the best close method for thr httpCli in this case ? > (abort, closeAsync, close ..) > Paul -- To unsubscribe or change your settings for TWSocket mailing list please goto http://www.elists.org/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be
