Roch - PAE wrote:
> The delay can be inserted between 2 successive outgoing
> writes. The first write wakes up the peer (and starts a
> timer). A read, if issued, cancels the timer. But a second
> write shortly after a first one will not cause a wakeup of
> the peer; data is buffered. All like Nagle. Only difference
> is that instead of waiting for an ACK, we wait for a fix
> timer.
What is meant by "shortly?" So if the request response
is very quick, won't the same delay be still there? Maybe
I misunderstood the above. I guess pseudo code helps.
--
K. Poon.
[EMAIL PROTECTED]
_______________________________________________
networking-discuss mailing list
[email protected]
