Dan Poirier wrote: > 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).
Yes. I think there is also a bug in the buffer handling. If there is EAGAIN, the bytes whcih could not be sent are written int a buffer. But what happens if the next there is EAGAIN again? I think the old buffer is overwritten by the new bytes which could not be sent. btw: In my cases using TLS helps - apparently the socket/buffer handling in openssl is better than in sipp. regards klaus ------------------------------------------------------------------------- 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
