W3C home > Mailing lists > Public > public-webapps@w3.org > October to December 2011

Re: Spec changes for LCs and later maturity levels [Was: Re: RfC: LCWD of Web Socket API; comment deadline October 21]

From: Ian Hickson <ian@hixie.ch>
Date: Mon, 10 Oct 2011 22:30:35 +0000 (UTC)
To: Arthur Barstow <art.barstow@nokia.com>
Cc: Julian Reschke <julian.reschke@gmx.de>, public-webapps <public-webapps@w3.org>
Message-ID: <Pine.LNX.4.64.1110102229430.20981@ps20323.dreamhostps.com>
On Sun, 9 Oct 2011, Arthur Barstow wrote:
> On 10/7/11 8:32 AM, ext Julian Reschke wrote:
> > As far as I recall, we agreed in the IETF WG that parsing of web socket URIs
> > should work exactly the same way as for any other URI scheme. It appears
> > that the API spec now tries to override this, and this looks problematic to
> > me.
> On 10/7/11 9:30 AM, ext Arthur Barstow wrote:
> > In [1], Julian asks about Web Socket API rev 1.247 [2], the change that adds
> the Parsing WebSocket URLs section (CVS comment "Revert the part of r5409 that
> removed the URL parsing algorithms, since it's no longer defined in the
> protocol spec. (whatwg r6632)").
> >
> > Would you please elaborate on this change?
> 
> On 10/7/11 11:28 AM, ext Ian Hickson wrote:
> > Elaborate in what way?
> 
> Why is the override in 1.247 needed, given what Julian indicates above?

There's no override. It's just defining how you do it because nothing else 
defines it.

-- 
Ian Hickson               U+1047E                )\._.,--....,'``.    fL
http://ln.hixie.ch/       U+263A                /,   _.. \   _\  ;`._ ,.
Things that are impossible just take longer.   `._.-(,_..'--(,_..'`-.;.'
Received on Monday, 10 October 2011 22:34:41 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 18:49:48 GMT