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

[Bug 18611] Blob should support Transferable

From: <bugzilla@jessica.w3.org>
Date: Fri, 24 Aug 2012 23:02:33 +0000
Message-Id: <E1T52td-0004uC-77@jessica.w3.org>
To: public-webapps-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=18611

--- Comment #8 from Glenn Maynard <glenn@zewt.org> 2012-08-24 23:02:32 UTC ---
(In reply to comment #7)
> I disagree. The concept of transferrable is highly visible in the case of
> ArrayBuffer since performance is different from when copying+closing the
> ArrayBuffer.

The testable, deterministic, specified behavior on scripts is identical. 
Performance is an implementation detail, and probably won't even apply in every
case (eg. a process-model browser might optimize cross-thread messaging in this
way but not cross-process).  It seems a bit odd to not give a consistent API
for things that act the same just because the underlying optimizations differ.

> The concept of transferrable is also very different in the case of MessagePorts
> because the port isn't actually closed, it's, well, transferred.

MessagePorts are a different beast entirely.  (They're Transferable for other
reasons--API backwards-compatibility, and maintaining the invariant that
structured clone doesn't mutate its input of objects not in the transfer list.)

-- 
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 Friday, 24 August 2012 23:02:38 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 24 August 2012 23:02:40 GMT