- From: <bugzilla@jessica.w3.org>
- Date: Wed, 04 Feb 2015 07:10:42 +0000
- To: public-html-admin@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=27955
Bug ID: 27955
Summary: share an immutable object between threads
Product: HTML WG
Version: unspecified
Hardware: PC
OS: All
Status: NEW
Severity: normal
Priority: P2
Component: HTML5 spec
Assignee: dave.null@w3.org
Reporter: charlie651@gmail.com
QA Contact: public-html-bugzilla@w3.org
CC: mike@w3.org, public-html-admin@w3.org,
public-html-wg-issue-tracking@w3.org
"The steps will return a new object of the same type, and will permanently
neuter the original object. "
It would be nice to have a way to make an arraybuffer available for reading
both to a worker thread and to the main thread for reading without duplicating
it in memory.
Sending it as a message will duplicate it, and transferring it will neuter it
making it unavailable to the main thread.
If we can make the ArrayBuffer read only, we should be able to share it between
the worker and code in the main thread while preserving thread safety.
Maybe a syntax like worker.postMessage(message, [transfers], [shares])?
--
You are receiving this mail because:
You are on the CC list for the bug.
Received on Wednesday, 4 February 2015 07:10:44 UTC