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: Tue, 19 Jun 2012 15:00:29 +0000
To: public-audio@w3.org
Message-Id: <E1Sgzuv-0006qR-Fl@jessica.w3.org>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=17415

--- Comment #25 from Marcus Geelnard (Opera) <mage@opera.com> 2012-06-19 15:00:28 UTC ---
(In reply to comment #23)
> (In reply to comment #21)
> Of course, but this argument is just as valid against having an audio API at
> all, after all the developer can't anticipate what else is running on the
> user's computer aside from the browser. For all the developer knows, the API
> might be running on a mobile browser with all cores (or maybe just one) busy.
> Throwing more threads at it doesn't necessarily solve the problem of not being
> able to anticipate all situations.

True, but there is a significant difference between running several threads on
a single core (preemptive scheduling should give any thread CPU quite often),
and running several pages in a single thread (a callback may have to wait for
seconds).

-- 
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 Tuesday, 19 June 2012 15:00:37 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 19 June 2012 15:00:37 GMT