W3C home > Mailing lists > Public > public-webapps@w3.org > April to June 2011

Re: [websockets] What needs to be done before the spec is LC ready?

From: Adam Barth <w3c@adambarth.com>
Date: Tue, 5 Apr 2011 11:32:21 -0700
Message-ID: <BANLkTi=o-tG0LzR4Gp20nxnDB5w=5HOYDg@mail.gmail.com>
To: Ian Hickson <ian@hixie.ch>
Cc: Arthur Barstow <art.barstow@nokia.com>, public-webapps <public-webapps@w3.org>, ifette@google.com
There's also potentially protocol changes that will cause use to need
to fix things at the API layer.  For example, if the IETF introduces
redirects into the protocol, we'll likely need to account for them at
the API layer:

http://lists.whatwg.org/htdig.cgi/whatwg-whatwg.org/2011-March/031070.html

Adam


On Tue, Apr 5, 2011 at 10:15 AM, Ian Hickson <ian@hixie.ch> wrote:
> On Tue, 5 Apr 2011, Arthur Barstow wrote:
>>
>> What needs to be done before the WebSocket API is LC ready?
>
> I'm currently waiting for a number of editorial changes to the protocol
> specification to provide hooks for the API specification so that I can
> update the API apecification to work with the new protocol.
>
>
>> 3. The definition of "absolute url" makes https:foo not an absolute url, since
>> its behavior depends on whether the base is https: or not. Is that desired?
>> ...
>>    http://www.w3.org/Bugs/Public/show_bug.cgi?id=10213
>
> This particular bug is blocked on there being a specification that defines
> how URLs work. Last I heard, Adam was going to be writing it. I would also
> be unblocked if the IRI work at the IETF were to actually happen (it was
> supposed to happen about 2 years ago now). There was a also a recent HTML
> WG decision to put the requirements into the HTML spec. The decision
> starts with text that is known to be broken and so also requires editing
> work; however, it's possible that I'll end up updating that before Adam's
> work is done, in which case I'll use that instead.
>
> Either way this particular bug isn't likely to be fixed in a hurry. In
> practice it's not a huge blocker; in fact I'm not sure it's a blocker at
> all, as it is possible that the WebSocket protocol spec now defines how
> this issue is handled anyway, in which case the bug won't actually block
> the API spec. I'll find out when the edits to the protocol spec are done
> and I get to update the API spec for the new protocol spec.
>
> --
> Ian Hickson               U+1047E                )\._.,--....,'``.    fL
> http://ln.hixie.ch/       U+263A                /,   _.. \   _\  ;`._ ,.
> Things that are impossible just take longer.   `._.-(,_..'--(,_..'`-.;.'
>
Received on Tuesday, 5 April 2011 18:33:20 GMT

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