[Bug 13178] New: binaryType should be immutable after connection is established


           Summary: binaryType should be immutable after connection is
           Product: WebAppsWG
           Version: unspecified
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: WebSocket API (editor: Ian Hickson)
        AssignedTo: ian@hixie.ch
        ReportedBy: adrianba@microsoft.com
         QAContact: member-webapi-cvs@w3.org
                CC: mike@w3.org, public-webapps@w3.org

Microsoft proposes that:

  1. As proposed in 12816 [1] - Make second argument in constructor
     an object for future extensibility - a property bag is added to
     the constructor.

  2. The property bag initially includes protocols and binaryType.

  3. The binaryType is immutable after the connection is established.
     The binaryType attribute is read only.

As discussed in Bug 12102 [2] -WebSocket protocol update time  if there is a
significant need to allow binaryType to be changed after a connection is
established, then it can be enabled in the next version.  Currently, it is
introducing complexity and potential performance impacts into the
implementation without clear scenarios. There is also a mitigation of using
ArrayBuffer<->Blob conversion routines. 

[1] http://www.w3.org/Bugs/Public/show_bug.cgi?id=12816
[2] http://www.w3.org/Bugs/Public/show_bug.cgi?id=12102#c40

Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.

Received on Thursday, 7 July 2011 19:56:31 UTC