On Mon, Dec 15, 2008 at 1:06 PM, Jeanfrancois Arcand
<Jeanfrancois.Arcand_at_sun.com> wrote:
> Salut,
<snip/>
> Just to be sure, is it a regression? Grizzly 1.0 doesn't supports HTTP
> Pipelining so unless you read the body, grizzly will blocks waiting for that
> body to be read until the next request gets parsed.
>
> Comet could be used as that one support http pipelining, although I suspect
> we might have issues.
>
I'm not exactly sure what you're talking about here.
Are you saying Grizzly 1.0 is the one found in Glassfish v2 ur2?
I do read the body, I can see the chunked encoded gzip blocks. As I
said, I can read usually read the first 2 to 4 responses then a long
blocking read waiting for bytes from the client followed by a
connection close.
Or are you saying Grizzly in this Glassfish release doesn't support
HTTP pipelining? Because it does respond to HTTP 1.1 requests versus
setting 1.0 for the version. I had assume that because of this, it
would support pipelining since it's a mandatory feature of HTTP 1.1.