[e2e] TCP out of order
dennis at juniper.net
Tue Jan 22 12:25:54 PST 2002
> this is classic with silly window syndrome, and there are specific
> mechanisms in TCP implementations to avoid that. In short, TCP doesn't send
> partial segments unless triggered in some way, such as no longer having
> anything outstanding (Nagle's algorithm) or getting an API "push" event.
Ah, yes, I actually knew that but I'm getting old and forgetful. I once
understood a circumstance where such packets were generated consistently,
since we had a situation where the behaviour was repeatable, but I've
forgotten that as well and was reduced to guessing.
More information about the end2end-interest