W3C home > Mailing lists > Public > ietf-http-wg@w3.org > October to December 2016

RE: Early Hints (103)

From: Mike Bishop <Michael.Bishop@microsoft.com>
Date: Wed, 30 Nov 2016 19:41:05 +0000
To: Patrick McManus <mcmanus@ducksong.com>, HTTP Working Group <ietf-http-wg@w3.org>
Message-ID: <BN6PR03MB27085A94015460A4E0349EFB878C0@BN6PR03MB2708.namprd03.prod.outlook.com>
Strongly support.  It’s useful and exactly what this class of responses was intended for.  Let’s do it – and fix the bugs we flush out at the same time.

From: Patrick McManus [mailto:mcmanus@ducksong.com]
Sent: Tuesday, November 22, 2016 2:27 PM
To: HTTP Working Group <ietf-http-wg@w3.org>
Subject: Early Hints (103)

Dear Gentlefolk of HTTPbis,
This is a followup to Kazuho's presentation in Seoul[*] where he discussed https://datatracker.ietf.org/doc/draft-kazuho-early-hints-status-code/

The idea seemed to have acceptance (both in the room and on the list) with some concerns expressed about interoperability. Kazuho was kind enough to publish an endpoint so you can test if the client you implement has an unexpected failure in the face of 103.
However, the draft was published pretty close to meeting time and there wasn't much space for discussion in the room. So before we do a Call For Adoption, I would like to hear some more discussion so the chairs can be confident there is interest - even if that discussion is "I would like to implement that" or "what does that accomplish?". Please do chime in, your silence will be taken for disinterest otherwise :).

-Patrick
[*] http://recs.conf.meetecho.com/Playout/watch.jsp?recording=IETF97_HTTPBIS&chapter=chapter_1 goto 1:43 mark
Received on Wednesday, 30 November 2016 19:41:41 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 30 November 2016 19:41:44 UTC