- From: Ian Hickson <ian@hixie.ch>
- Date: Mon, 18 Jul 2011 18:42:14 +0000 (UTC)
- To: Harald Alvestrand <harald@alvestrand.no>
- cc: public-webrtc@w3.org
On Mon, 18 Jul 2011, Harald Alvestrand wrote: > > - There is an API object (JSON object?) called "hints" that the Web app > can send to the browser to influence these choices - probably a > parameter to the calls that add or modify streams. This is already done. > - In version 1.0 of the spec, the content of this object is left > undefined, possibly with some reserved semantics for "if you want to > experiment, use this kind of name for your attribute". I don't see why we'd leave it undefined, that would just mean that the API of whichever browser first gets traction on this is the API we end up using. Based on our experience with this kind of thing in the past, I think the current approach of a well-defined but extensible hints argument is better. > - We iterate once the rest of the spec is reasonably stable. Indeed. -- Ian Hickson U+1047E )\._.,--....,'``. fL http://ln.hixie.ch/ U+263A /, _.. \ _\ ;`._ ,. Things that are impossible just take longer. `._.-(,_..'--(,_..'`-.;.'
Received on Monday, 18 July 2011 18:42:47 UTC