- From: Olivier Thereaux <notifications@github.com>
- Date: Wed, 11 Sep 2013 07:29:47 -0700
- To: WebAudio/web-audio-api <web-audio-api@noreply.github.com>
Received on Wednesday, 11 September 2013 14:30:37 UTC
> [Original comment](https://www.w3.org/Bugs/Public/show_bug.cgi?id=17415#10) by Olli Pettay on W3C Bugzilla. Wed, 13 Jun 2012 16:06:02 GMT Not quite the same thing as audio processing, but we're trying to limit all the new XHR features in main thread to async only. Sync is occasionally easier to use, but it will just fail (cause bad user experience) in the main thread. (And yes, the change to limit certain sync behavior to workers only broke various libraries.) Similarly, JS audio processing is guaranteed to fail on the main thread in reasonable common cases. So, IMHO, all the JS audio processing should happen in background threads. --- Reply to this email directly or view it on GitHub: https://github.com/WebAudio/web-audio-api/issues/113#issuecomment-24244356
Received on Wednesday, 11 September 2013 14:30:37 UTC