This is often problem during slow server respons. Assuming POP3 service with preset relatively small timeout (1-5 sec). After connection and sending any command, data will be read from socket correctly until server delays exceed preset timeout value. That is unfortunate, since undelivered (delayed) data will be delivered later and available in the socket buffer before next command is sent. On next command, first will be received these previously undelivered data!
That is unfortunate, since LIST may return result of STAT, or any other previous command. It would be practical to clean socket buffer before command is sent. Also having minimum timeout value limit by application (at least e.g 10 sec) will decrease possibility of arising mentioned problem, however it will not solve it entirely, since we cannot estimate when server will actually respond on sent command. 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
