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:30:23 -0700
To: WebAudio/web-audio-api <web-audio-api@noreply.github.com>
Message-ID: <WebAudio/web-audio-api/issues/113/24244816@github.com>
> [Original comment](https://www.w3.org/Bugs/Public/show_bug.cgi?id=17415#91) by Philip J├Ągenstedt on W3C Bugzilla. Mon, 06 Aug 2012 14:46:03 GMT

(In reply to [comment #91](#issuecomment-24244810))
> On the "must happen in Workers" side, I mostly see (in e.g Marcus' Comment #3)
> the idea that we should make sure not to let developers do anything bad. I am
> not fully confortable with that - thought our job was to enable and empower,
> and if need be to document best practices.

I don't understand what those best practices would be, since Web developers aren't in a position to avoid the problems with a main thread callback API. They cannot control what goes on in other tabs, and as I mentioned in comment 9 and comment 19, those tabs can block the main thread for longer than even the maximum buffer size allowed by JavaScriptAudioNode.

That being said, perhaps we should begin to focus on what a WorkerAudioNode would look like, since that's what we want to actually implement.

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

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