If possible, I would encourage any breaking update to WebSockets (protocol or JS API) to be feature detectable. Additionally, I would encourage WebKit to postpone updating to -09 to coincide with expected changes to the JS API, which may provide the necessary feature detection mechanisms (e.g., WebSocket.open a la XHR): http://www.w3.org/Bugs/Public/show_bug.cgi?id=12102.
More specifically, I work at HP Palm and our devices currently support the -00 implementation of WebSockets, and while we are able to auto-update, users must approvebut may not have been updated, and while as far as I understand being just a protocol -00 could be detected and supported server-side along-side -09, -00 implementations connecting to a -09 server will have to fail (full RTT) in order to feature detect support for -09. Allowing this feature detection along-side the protocol-break would enable libraries and implementations to know what protocol versions are supported and adjust behavior accordingly. Alternatively, being that the protocol updates are in draft while API updates are not with no anticipation of when they will be, some other means of feature detection could be exposed instead. Cheers, Adam Crabtree
_______________________________________________ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev