> 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.
Yes, of course! I still not uderstand what you wish to tell us, because all synapse applications are designed by this way! > It is on you to decide, I just reported inconsistency and problems. But you have a problem and YOU have a incosistency, becaouse YOu are doing thinks badly and by different way then us, and now you are writing thinks where you found your way as problematic and proposing our way instead? :-O You are proposed thinks to me, but this thinks I am using from Synapse's born. -- Lukas Gebauer. E-mail: [EMAIL PROTECTED] http://synapse.ararat.cz/ - Ararat Synapse - TCP/IP Lib. ------------------------------------------------------------------------- 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
