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
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:
On Tue, 5 Apr 2011, Adam Barth wrote:
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:
On Tuesday, April 05, 2011 4:27 AM, Arthur Barstow wrote:
Hi All,
What needs to be done before the WebSocket API is LC ready?
Bugzilla has three open bugs for this spec:
1. API for send/receive of binary data? Current IETF protocol drafts
have binary type. Consider typed arrays
