- From: Ehsan Akhgari <ehsan.akhgari@gmail.com>
- Date: Thu, 27 Jun 2013 16:41:19 -0400
- To: David Herman <dherman@mozilla.com>
- Cc: "public-audio@w3.org" <public-audio@w3.org>
Received on Thursday, 27 June 2013 20:42:32 UTC
On Thu, Jun 27, 2013 at 3:38 PM, David Herman <dherman@mozilla.com> wrote: > Robert O'Callahan wrote: > > > The status quo in Webkit, as I understand it, allows changes to the array > > after the setValueCurveAtTime call to affect the AudioParam's behavior on > > the audio thread, so those changes may or may not be observed depending > on > > all sorts of implementation details, including details of the memory > > subsystem of the underlying hardware. This is unprecedented in existing > > specs and I will object to it all the way through the W3C process if > > necessary. > > I would like to back Robert up and voice my objections to the racy API. We > should not be adding low-level data races to JavaScript or the web > platform, nor should we be exposing architecture-specific memory models. > I'm in the same boat, as I've said in previous discussions on this matter on the list. -- Ehsan <http://ehsanakhgari.org/>
Received on Thursday, 27 June 2013 20:42:32 UTC