Re: [hybi] With deflate-stream, Close frame doesn't work as an end of data marker

[Andy Green <[e-mail]>]

On 03/09/2011 09:51 PM, Somebody in the thread at some point said:

Hi -

>  > Are there other circumstances that can actually cause this I'm
>  > overlooking too easily?
>
> Yes. Since your receive buffer passed in recv(2) has a predetermined
> finite size and you may not be reading all data in the kernel space
> (TCP) buffer. Depending on how it is implemented and timing, the
> receiver may successfully extract Close frame out of data you have just
> read from TCP socket, and then close the socket without bothering to
> read the outstanding data in the kernel.

It's a good point.  I can see how that's effectively fragmenting the 
thing entirely in userland at the receiver.

However that seems simple to solve since the extra junk data is already 
received in kernel.  Just before socket close time we just need to use a 
little poll() POLLIN loop with no timeout to drain it while there's 
stuff immediately pending, right?  Nothing more will come and close is 
always happy.

-Andy