W3C home > Mailing lists > Public > public-webapps@w3.org > July to September 2011

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

From: <bugzilla@jessica.w3.org>
Date: Fri, 08 Jul 2011 20:09:33 +0000
To: public-webapps@w3.org
Message-Id: <E1QfHMj-0000xC-Jc@jessica.w3.org>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=13178

Ian 'Hixie' Hickson <ian@hixie.ch> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
                 CC|                            |ian@hixie.ch
         Resolution|                            |WONTFIX

--- Comment #4 from Ian 'Hixie' Hickson <ian@hixie.ch> 2011-07-08 20:09:32 UTC ---
Comment 1 is correct.

Note that the spec does handle the blob->arraybuffer case by allowing UAs to
delay events accordingly.

Having a boolean to control whether the next packet is blob or not doesn't
really make sense for two reasons: First, the default has to be blob to avoid
big binary packets from taking memory up by default. That is, blob is the
better default. Second, it wouldn't help the problem. You don't know what the
next packet will be until you handle the message for the previous one, by which
time the UA has almost certainly already started receiving the next packet.

-- 
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 Friday, 8 July 2011 20:09:35 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 18:49:46 GMT