Re: [hybi] I-D ACTION:draft-ietf-hybi-thewebsocketprotocol-08.txt

Ian Fette (イアンフェッティ) <> Thu, 09 June 2011 02:17 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id CB2B311E80D9 for <>; Wed, 8 Jun 2011 19:17:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -105.428
X-Spam-Status: No, score=-105.428 tagged_above=-999 required=5 tests=[AWL=0.248, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id 2BLtiEhEvcim for <>; Wed, 8 Jun 2011 19:16:59 -0700 (PDT)
Received: from ( []) by (Postfix) with ESMTP id 0A71211E8074 for <>; Wed, 8 Jun 2011 19:16:58 -0700 (PDT)
Received: from ( []) by with ESMTP id p592GwdW010259 for <>; Wed, 8 Jun 2011 19:16:58 -0700
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed;; s=beta; t=1307585818; bh=WdGtqdUu3+jX7SlIJUqekF6JOLY=; h=MIME-Version:Reply-To:In-Reply-To:References:Date:Message-ID: Subject:From:To:Cc:Content-Type; b=NLY4r2Ohoax6wgU4/8iPAc9TOhuoyiNHUDbliFyqRkurE6IA3sqZa4/JtdtSdZK6X o8UUzLSmoNhIbFbyPFWsw==
Received: from qwj9 ( []) by with ESMTP id p592Giww001197 (version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=NOT) for <>; Wed, 8 Jun 2011 19:16:57 -0700
Received: by qwj9 with SMTP id 9so735454qwj.21 for <>; Wed, 08 Jun 2011 19:16:57 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=beta; h=domainkey-signature:mime-version:reply-to:in-reply-to:references :date:message-id:subject:from:to:cc:content-type; bh=7WNoBjtzu/3L46q4NbZNkWZ1tgAa9Z+ocWn820bcOG8=; b=m3u0bXJZYprxFoEfqOXdBYmBRyIBY4ZeuqiY4Fy2PRyF/n/Iypk6Gs+VQlmqFrK9pg u9vwIJrWTdt3D1hABK7w==
DomainKey-Signature: a=rsa-sha1; c=nofws;; s=beta; h=mime-version:reply-to:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; b=XTlQ7nHNdxvCsM2L826G68iEG08l/m7SRV71wM0g5ZzqJedkIejYUF/OSXQqqTZXIu WuN3EOVQSnYvMyKh+0gw==
MIME-Version: 1.0
Received: by with SMTP id u14mr115667qcq.29.1307585816810; Wed, 08 Jun 2011 19:16:56 -0700 (PDT)
Received: by with HTTP; Wed, 8 Jun 2011 19:16:56 -0700 (PDT)
In-Reply-To: <>
References: <> <> <> <> <> <> <>
Date: Wed, 8 Jun 2011 19:16:56 -0700
Message-ID: <>
From: =?UTF-8?B?SWFuIEZldHRlICjjgqTjgqLjg7Pjg5Xjgqfjg4Pjg4bjgqMp?= <>
To: Bjoern Hoehrmann <>
Content-Type: multipart/alternative; boundary=000e0cd5f4aa1fd71204a53e0c3f
X-System-Of-Record: true
Cc: "" <>, Gabriel Montenegro <>, Greg Wilkins <>
Subject: Re: [hybi] I-D ACTION:draft-ietf-hybi-thewebsocketprotocol-08.txt
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Server-Initiated HTTP <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Thu, 09 Jun 2011 02:17:00 -0000

On Wed, Jun 8, 2011 at 6:08 PM, Bjoern Hoehrmann <> wrote:

> * Ian Fette wrote:
> >From the W3C side, Hixie and I have gone over it and he just published a
> new
> >API spec a day or two ago that properly lines up the two documents.
> I think it is good that you help "Hixie" with his editing duties. But we
> do need to know if there are any problems with the documents we work on.
> I have not seen a representative of the W3C tell us of any problems, or
> tell us they reviewed the draft and found no problems. In either case, I
> would expect there to be mails in the list archive detailing either, but
> I am not aware of, and haven't found when searching, any to this end. If
> "Hixie" did provide comments on our documents, I would welcome pointers
> to them.

Hixie is the editor of the HTML spec. He pointed out problems, they were
addressed. I've a series of emails from him that I am happy to share if he
does not mind (there's nothing private in them, but I don't make a habit of
forwarding private correspondence.) As we have the luxury of meeting
face-to-face, there were also face-to-face discussions to resolve stickier
issues, along with a few late night IRC sessions on #whatwg.

Largely the issues were not substantive. The spec has not changed much from
the API perspective, the exception being exposing the extensions that were
negotiated in the handshake via the API, and some semantics around whether
onError() is necessary or not and how that interacts with the WebSocket
Close Status Codes. That has been aligned in his latest spec. The rest was
just "I need hooks for this" e.g. "How do I send data? What is the algorithm
/ section of the spec I reference to send data?".

Finally, I'm not sure what you expect to get from W3C that you're not
getting from the people on this list. You've got the people implementing the
API watching this list, that's the same subset of the people from W3C that
would provide meaningful commentary about the spec.

> --
> Björn Höhrmann · ·
> Am Badedeich 7 · Telefon: +49(0)160/4415681 ·
> 25899 Dagebüll · PGP Pub. KeyID: 0xA4357E78 ·