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

[Bug 17415] (JSWorkers): JavaScriptAudioNode processing in workers

From: <bugzilla@jessica.w3.org>
Date: Fri, 27 Jul 2012 16:56:22 +0000
Message-Id: <E1Sunpu-0003x7-Ku@jessica.w3.org>
To: public-audio@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=17415

--- Comment #74 from Grant Galitz <grantgalitz@gmail.com> 2012-07-27 16:56:18 UTC ---
(In reply to comment #64)
> (In reply to comment #62)
> > (In reply to comment #59)
> > > Would the following be a correct conclusion?:
> > > 
> > > - Audio processing in JavaScript should be done in workers.
> > […]
> > 
> > I think that is a reasonable conclusion, yes - although there may be objections
> > by e.g Philip who seemed to be quite adamant about it (See Comment #2). 
> 
> Nope, I think that JavaScript processing should be done in workers, and only
> workers.

Problem lies with the web worker being restricted from accessing all the APIs
the main thread has access too. If I house everything in the worker, doing so
will mess up some other components not audio related.

-- 
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 Friday, 27 July 2012 16:56:23 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 27 July 2012 16:56:24 GMT