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:53 -0700
To: WebAudio/web-audio-api <web-audio-api@noreply.github.com>
Message-ID: <WebAudio/web-audio-api/issues/113/24244423@github.com>
> [Original comment](https://www.w3.org/Bugs/Public/show_bug.cgi?id=17415#20) by Robert O'Callahan (Mozilla) on W3C Bugzilla. Mon, 18 Jun 2012 23:39:06 GMT

(In reply to [comment #20](#issuecomment-24244414))
> 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.

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

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