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: Mon, 18 Jun 2012 23:39:07 +0000
To: public-audio@w3.org
Message-Id: <E1SglXH-0002AF-9r@jessica.w3.org>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=17415

--- Comment #21 from Robert O'Callahan (Mozilla) <roc@ocallahan.org> 2012-06-18 23:39:06 UTC ---
(In reply to comment #20)
> Developers have to be conscious about performance and avoiding layout reflows
> anyway, why should this API be any different?

One problem is that developers don't control all the pages that might possibly
be sharing the same thread. No browser puts every page on its own thread. So
even if you write your page perfectly, you're still vulnerable to latency
caused by poorly-written pages sharing your main thread.

-- 
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, 18 June 2012 23:39:10 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 18 June 2012 23:39:15 GMT