Re: WebSocket over HTTP2 RFC6455 conformance from Martin Thomson on 2014-02-20 (ietf-http-wg@w3.org from January to March 2014)

From: Martin Thomson <martin.thomson@gmail.com>
Date: Thu, 20 Feb 2014 09:11:21 -0800
To: Takeshi Yoshino <tyoshino@google.com>
Cc: Yutaka Hirano <yhirano@google.com>, HTTP Working Group <ietf-http-wg@w3.org>
Message-ID: <CABkgnnV9bovz0VCFYE+=wLn-2LcFuhs--AkBLxqcKgHVKoTzHg@mail.gmail.com>

On 19 February 2014 21:57, Takeshi Yoshino <tyoshino@google.com> wrote:
> Also, reusing the identifier "RSV1-3" we now have in RFC6455 for those
> booleans (not pointing syntax. not pointing 1 bit serialization. but
> semantics) eases writing extensions that work for both RFC6455 and
> WS/HTTP/2.0. This is not-so-important but another concern Yutaka and HyBi
> people should have.

I don't consider those booleans to be part of the websocket semantics.
 They certainly don't surface at the API level.

Received on Thursday, 20 February 2014 17:11:52 UTC