From: Billy Chasen (billy.chasen_at_[hidden])
Date: 2008-04-05 20:14:55
A faulty client shouldn't mess up a server (I'm trying to build a robust server)
I changed the async_read_until calls to async_read_some and now it
works perfectly
The client purposely wasn't waiting -- it just kept sending data
(simulating a bad client)
On Fri, Apr 4, 2008 at 3:39 AM, Christopher Kohlhoff <chris_at_[hidden]> wrote:
> 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
>
>
> _______________________________________________
> Unsubscribe & other changes: http://listarchives.boost.org/mailman/listinfo.cgi/boost
>