W3C home > Mailing lists > Public > public-webapps-bugzilla@w3.org > August 2012

[Bug 18611] Blob should support Transferable

From: <bugzilla@jessica.w3.org>
Date: Sat, 18 Aug 2012 06:37:04 +0000
Message-Id: <E1T2cee-0003vw-Bp@jessica.w3.org>
To: public-webapps-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=18611

Charles Pritchard <chuck@jumis.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |chuck@jumis.com

--- Comment #3 from Charles Pritchard <chuck@jumis.com> 2012-08-18 06:37:04 UTC ---
(In reply to comment #1)
> Transferability has been added twice before: Ports and "ArrayBuffer-stuff".
> 
> In the first occasion it was added because Ports doesn't make sense if they
> aren't transferred.
> 
> In the second occasion it was added to enable better performance.
> 
> Neither of those reasons apply here. We would get no additional performance
> benefits from transferring blobs, and we can implement posting Blobs just fine
> without transferring them.


We've got discussion about Blob with autorelease as well as transferring Blobs
across origins (because we can't just sent a simple filesystem URI) and the
consequences among all existing implementations in keeping Blob references in
memory and on many occasions, Blobs in RAM.

-- 
Configure bugmail: https://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
Received on Saturday, 18 August 2012 06:37:06 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Saturday, 18 August 2012 06:37:08 GMT