> Then set timeout for much higher value. However if you not got any > data packet over 60 seconds, even you are on telephone line, then is > really somethink bad on your connection. Do not argument with slow > tepelone lines, I was using it before a few years too, and i was > using synapse over slow telephone lines for years without any > problems!
My argument here is that received buffer stays full if anythigh goes wrong and will be read after new command is sent. If timeout is policy to detect broken line, in that moment socket connection should be manually closed. Otherwise mentioned problem is present. I can easily forbit to user to set timeout as mentioned, but that is not a point. Second, when line is phisically broken, after Dial-up reconnect and trying to connect to (POP3) server from still active application, application will freeze, as long buffer is full - USER command will return existed data in buffer... Currently, application must be closed in order to free the buffer. It is on you to decide, I just reported inconsistency and problems. Sasa -- www.szutils.net ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ synalist-public mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/synalist-public
