> If it is of any comfort, this sometimes happens to me too. Like you, I've > never been able to find any reason for it happening. One remote > possibility I can think of is that since we're dealing with blocking > sockets, it is quite possible that the socket layer itself gets stuck on a > level that is outside the scope of Synapse. Unfortunately, I have no > solution to this other than "if it fails, try it again after a while".
Even Synapse using blocking sockets, it trying to call reading operations as non-blocking. For example, it do not call read operations for larger count of bytes then what is pending for read in socket stack, etc. So, I never got unconditional 'stuck', because Timeout property is working in this case. However it have exceptions. Connect call have hardwired timeout in operating system, and some thirdparty programs (what modifying socket stacks) can break it at all. (antiviruses, firewall, VPN software,... all these application can modify how winsock works!) For example, is known mysterious problems with NOD32. -- Lukas Gebauer. E-mail: [EMAIL PROTECTED] WEB: http://www.ararat.cz/synapse - Synapse Delphi and Kylix TCP/IP Library ------------------------------------------------------------------------- This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone _______________________________________________ synalist-public mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/synalist-public
