Confirm
716
edits
Changes
→WebSockets
There is a separate WebSockets API maintained at the W3C. (The [http://dev.w3.org/html5/websockets/ editor's draft] is the best source of information and contains the most recent API. The API is message-based. That is, individual WebSocket frames are sent as messages via an event handler in JavaScript. Messages can be handled as strings, ArrayBuffers or Blobs.
As of '''Firefox 11''' we've unprefixed the WebSockets API. This means that we don't expect the protocol or the API to change. In other words, we're basically "done" with our WebSockets support. The one outstanding item that I know about is the fact that if you download a large binary message as a Blob, we don't stream the data to disk, but instead back the Blob using an in-memory buffer. This is transparent to the page, but causes us to use more memory. Tracking bug is {{bug|704447}}.
= Asset Management =
