W3C home > Mailing lists > Public > ietf-http-wg@w3.org > July to September 2014

Re: HTTP/2 response completed before its request

From: Greg Wilkins <gregw@intalio.com>
Date: Wed, 2 Jul 2014 09:09:06 +0200
Message-ID: <CAH_y2NHiwVgDK9uxVORPvdLNWsEfF5god7ASHer=wqmvDLQ2=w@mail.gmail.com>
To: Martin Thomson <martin.thomson@gmail.com>
Cc: William Chan (ι™ˆζ™Ίζ˜Œ) <willchan@chromium.org>, Jesse Wilson <jesse@swank.ca>, HTTP Working Group <ietf-http-wg@w3.org>
On 1 July 2014 20:41, Martin Thomson <martin.thomson@gmail.com> wrote:

> The stall is half of the problem, but do you cancel the send as well?
> If the server has provided a response and closed the stream, there is
> no point in continuing to send them data.  Especially if they forget
> to send window updates.
>

I don't agree.  It is certainly possible to write server application code
that commits a response and then processes the request data.     It's not a
very good way of doing it and probably invites all sorts of application
races.... but i don't think the transport layer can conclude that it is
necessarily a bad thing.


regards




-- 
Greg Wilkins <gregw@intalio.com>
http://eclipse.org/jetty HTTP, SPDY, Websocket server and client that scales
http://www.webtide.com  advice and support for jetty and cometd.
Received on Wednesday, 2 July 2014 07:09:49 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 30 March 2016 09:57:08 UTC