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

Re: WebSocket over HTTP2 RFC6455 conformance

From: Yutaka Hirano <yhirano@google.com>
Date: Fri, 21 Feb 2014 14:44:24 +0900
Message-ID: <CABihn6Ezf3kaQQ-qEKpMOeXmXzPkTJNUpiQmkb_XjPtGvWqpDw@mail.gmail.com>
To: Martin Thomson <martin.thomson@gmail.com>
Cc: HTTP Working Group <ietf-http-wg@w3.org>
Martin, is your answer "yes & no"?
All "semantics" words in my proposal are qualified as "the RFC6455
semantics" and it's not your "Websocket semantics".



On Thu, Feb 20, 2014 at 5:59 AM, Martin Thomson <martin.thomson@gmail.com>wrote:

> On 19 February 2014 06:11, Yutaka Hirano <yhirano@google.com> wrote:
> > At hybi, the following people answered "yes & yes".
>
> When you ask about semantics, you need to be more precise.
>
> My interpretation of "Websocket semantics" is the set of things that
> you can do with thewebsocketprotocol, or maybe the W3C WebSocket API.
> If your intent is to tunnel the protocol in a completely lossless
> fashion, then you are asking for more than just a preservation of
> semantics, you also want to preserve syntax.
>
> Note that we preserve syntax in HTTP/2 because there is a wealth of
> usage out there that relies on syntax, and even if we might think it
> unwise to do so, we are still unwilling to break those users.  It
> might be that the hybi group has people using those reserved bits such
> that preserving them is paramount, but websockets has far less history
> than HTTP.  I also didn't find the framing of the question or the
> responses to be particularly convincing.
>
Received on Friday, 21 February 2014 05:44:51 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:14:24 UTC