W3C home > Mailing lists > Public > public-audio@w3.org > July to September 2012

[Bug 17415] (JSWorkers): JavaScriptAudioNode processing in workers

From: <bugzilla@jessica.w3.org>
Date: Mon, 06 Aug 2012 14:46:08 +0000
Message-Id: <E1SyOZM-0007kw-9E@jessica.w3.org>
To: public-audio@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=17415

--- Comment #92 from Philip J <philipj@opera.com> 2012-08-06 14:46:03 UTC ---
(In reply to comment #91)
> On the "must happen in Workers" side, I mostly see (in e.g Marcus' Comment #3)
> the idea that we should make sure not to let developers do anything bad. I am
> not fully confortable with that - thought our job was to enable and empower,
> and if need be to document best practices.

I don't understand what those best practices would be, since Web developers
aren't in a position to avoid the problems with a main thread callback API.
They cannot control what goes on in other tabs, and as I mentioned in comment 9
and comment 19, those tabs can block the main thread for longer than even the
maximum buffer size allowed by JavaScriptAudioNode.

That being said, perhaps we should begin to focus on what a WorkerAudioNode
would look like, since that's what we want to actually implement.

-- 
Configure bugmail: https://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 Monday, 6 August 2012 14:46:11 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 6 August 2012 14:46:11 GMT