Consensus on the issue of deprecated APIs and sync decoding

Hi everyone,

Given today's teleconf <http://www.w3.org/2013/06/20-audio-minutes.html>,
let's see if we can reach consensus on a few issues.  I would appreciate if
everybody gave their opinion on the following.  Note that this only
concerns the unprefixed AudioContext API in all three engines, not
webkitAudioContext in Blink and WebKit.  I would appreciate if you can
respond to each proposal individually (i.e., it's OK to agree with one and
not with the other.)

1. I propose that we should remove this section <
https://dvcs.w3.org/hg/audio/raw-file/tip/webaudio/specification.html#OldNames>
from the spec, and any AudioContext implementation should not implement
those names.  If we get consensus on this, I will create a porting guide
documentation on MDN to help authors port their old content.  We can
mention the monkey patching library etc in that article, and make it really
useful for web developers.

2. I propose that we should remove the following AudioContext API:

AudioBuffer? createBuffer(ArrayBuffer buffer, boolean mixToMono);

If we get consensus about this, I will add this API to the aforementioned
article.

3. I need to write a separate proposal about the data race issues to make
sure that I'm not missing anything.  I'll try to do that tomorrow.

4. I propose that we agree that other than these changes, we start to
consider the API stable, with the caveats about the upcoming LC stage that
Olivier mentioned today in mind.  This means that I'm withdrawing my other
proposals about stylistic changes to the APIs, as I'm not very hopeful that
we can reach consensus over those in a reasonable time frame.

If you have any questions, please let me know.  I really appreciate if you
can respond in a timely manner, as it seems like most of the involved
browser vendors are very interested on reaching a consensus on these issues
very soon.

Cheers,
--
Ehsan
<http://ehsanakhgari.org/>

Received on Thursday, 20 June 2013 23:27:38 UTC