Re: [web-audio-api] Race Conditions (#66)

> [Original comment](https://www.w3.org/Bugs/Public/show_bug.cgi?id=22725#1) by Marcus Geelnard (Opera) on W3C Bugzilla. Mon, 29 Jul 2013 09:36:15 GMT

I think that the phrasing that Olivier proposed is a bit too close to agreeing on a final solution, but none of the proposed solutions are really ready yet (need more decisions and discussion).

I would like the phrasing to be slightly more more abstract, so that we can agree on a common mind-set for which we will solve the problems, for instance:

1. Keep the current API, with the shared memory solution. Specify the exact behavior in the Web Audio specification, and work together with other parties to work out what other specifications need to be updated/written, etc.

2. Based on RoC's proposal: Try to keep the current API, but remove any shared memory problems by using neutering as much as possible, and copying where necessary.

3. Based on Jer's proposal: Update the API in order to remove shared memory problems and make the interface more akin to existing Web interfaces.

Not sure if this is the best formulation - suggestions are welcome.

---
Reply to this email directly or view it on GitHub:
https://github.com/WebAudio/web-audio-api/issues/66#issuecomment-24244143