W3C home > Mailing lists > Public > public-audio@w3.org > April to June 2012

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

From: <bugzilla@jessica.w3.org>
Date: Wed, 13 Jun 2012 16:06:04 +0000
To: public-audio@w3.org
Message-Id: <E1Seq56-00050W-6R@jessica.w3.org>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=17415

Olli Pettay <bugs@pettay.fi> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |bugs@pettay.fi

--- Comment #11 from Olli Pettay <bugs@pettay.fi> 2012-06-13 16:06:02 UTC ---
Not quite the same thing as audio processing, but we're trying to limit
all the new XHR features in main thread to async only. Sync is occasionally
easier
to use, but it will just fail (cause bad user experience) in the main thread.
(And yes, the change to limit certain sync behavior to workers only broke
various libraries.)

Similarly, JS audio processing is guaranteed to fail on the main thread
in reasonable common cases. So, IMHO, all the JS audio processing
should happen in background threads.

-- 
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 Wednesday, 13 June 2012 16:06:13 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 13 June 2012 16:06:18 GMT