This is the loopback adapter we are talking about, we won't be flooding any "network" with that traffic.
On 12/21/05, Phillip Susi psusi@cfl.rr.com wrote:
Ge van Geldorp wrote:
I've been wrong before, but that's my interpretation of what's happening. We've only sent one byte and are trying to send another single byte.
Wait a second... why is it sending only one byte at a time? The caller is only send()ing one byte at a time? The caller really should not be doing that. You may be seeing the nagle algorithm kicking in then, which specifically tries to wait for an ack before sending more frames, _unless_ there is enough queued data to send another complete frame. This prevents tons of single byte frames from flooding the network, instead coalescing them into larger frames.
I'm curious now about the application. Why is it sending one byte at a time to itself via the loopback? That seems to be broken.
Ros-dev mailing list Ros-dev@reactos.org http://www.reactos.org/mailman/listinfo/ros-dev
-- <Russell> argh <Russell> iterator shenanigans :/