Looking at the source, it appears to me that when sipp gets back EAGAIN or EWOULDBLOCK on a TCP send, it writes to trace and counts it as congestion, but does nothing regarding trying again. (sipp.cpp, lines 1765 -- 1829).
------------------------------------------------------------------------- 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 _______________________________________________ Sipp-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/sipp-users
