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

Re: #535: No 1xx Status Codes

From: Greg Wilkins <gregw@intalio.com>
Date: Tue, 15 Jul 2014 18:58:47 +1000
Message-ID: <CAH_y2NFTWTP4DMaxCNYs1JqOCM8V+iwS7KZOui7Vua+bNMvgbg@mail.gmail.com>
To: Julian Reschke <julian.reschke@gmx.de>
Cc: Mark Nottingham <mnot@mnot.net>, HTTP Working Group <ietf-http-wg@w3.org>
Mark,

I'd like to see 100 semantic supported in h2, but it does not have to be
exactly by sending a :status:100.   I'm fine with dropping general 1xx
support.

I think there will be many real applications that just will not work over
h1-h2  proxies without 100 support.

I'm not a big fan of trailers and will ignore them in Jetty because there
is no way to plumb them into the servlet API.    However, I think there is
some value in leaving them (and mid stream meta data) in h2, as I think it
increases the chance that later extensions can be developed that will use
them and pass through intermediaries (but the frame should be called
METADATA rather than HEADERS), but this is very marginal.

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 Tuesday, 15 July 2014 08:59:14 UTC

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