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

Re: [web-audio-api] (JSWorkers): ScriptProcessorNode processing in workers (#113)

From: Olivier Thereaux <notifications@github.com>
Date: Wed, 11 Sep 2013 07:29:52 -0700
To: WebAudio/web-audio-api <web-audio-api@noreply.github.com>
Message-ID: <WebAudio/web-audio-api/issues/113/24244446@github.com>
> [Original comment](https://www.w3.org/Bugs/Public/show_bug.cgi?id=17415#24) by Marcus Geelnard (Opera) on W3C Bugzilla. Tue, 19 Jun 2012 15:00:28 GMT

(In reply to [comment #23](#issuecomment-24244435))
> (In reply to [comment #21](#issuecomment-24244423))
> 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).

---
Reply to this email directly or view it on GitHub:
https://github.com/WebAudio/web-audio-api/issues/113#issuecomment-24244446
Received on Wednesday, 11 September 2013 14:30:40 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:50:11 UTC