Chunked encoding doesn't always flush the terminating 0

Looks like JETTY-274 isn't fixed yet: with the SVN changes as of revision 1770, I have another reproducible case, this time with a better packet capture, hopefully.

In the attached capture, notice the three minute delay between packets #282 and #283, and that the only content in packet #283 is the terminating chunk length. The three minute delay is due to the client timeout: it closes the connection after three minutes, at which point jetty flushes the buffer. The data sat in the server the whole time.