Re: [hybi] web socket protocol in "last call"?

[Maciej Stachowiak <[e-mail]>]

On Oct 28, 2009, at 1:01 PM, Infinity Linden (Meadhbh Hamrick) wrote:

> wow. WS is in last call? not being able to continue work on putting
> something like RHTTP or BWTP over WS is a bit of a deal-breaker for
> me.
>
> but. i suppose there's no reason we can't work on BWTP independent of
> WS. i was just sorta hoping there would have been a way to coordinate
> these efforts.
>
> i guess there's also no reason now to meet at apachecon next week
> about WS. i mean, why bother meeting about something you can't change?


WHATWG Last Call doesn't mean "can't change". It's just soliciting  
comments. And it is in no way binding on the IETF.

In practice, the factor that will reduce the rate of change in the  
future will be when implementations (client-side and server-side) ship  
and Web content starts using it.

WebKit has an implementation of the WebSocket API and protocol in  
progress. We do not anticipate that work reaching a freeze point in  
the very near future. We'll think about taking appropriate measures to  
avoid locking in the protocol when we ship, to give the IETF Working  
Group a chance to define the protocol.

Given all this, I do think meeting in person to discuss is useful.

Regards,
Maciej