
4 Apr
2008
4 Apr
'08
7:39 a.m.
Billy Chasen wrote:
If I have a client send data to the server (which is using async_read_until)
If that client sends in a tight for-loop -- async_read_until returns garbled data.
If I put even the smallest delays in the loop, the server responds perfectly
Sounds suspiciously like a bug in the client. Does the client wait for each send to complete before starting the next one? Please illustrate how the "tight for-loop" works with some code. Cheers, Chris