- From: Stefan Håkansson LK <stefan.lk.hakansson@ericsson.com>
- Date: Tue, 19 Jul 2011 08:10:57 +0200
- To: "public-webrtc@w3.org" <public-webrtc@w3.org>
All, there has been some discussion lately on the list related to enabling the application to hint to the browser certain properties of the media scene (audio/voip, video resolution, video frame rate, ....). You may also have noted that I (in my individual contributor role) has been a bit negative; I advocate that we should do something simple without such support in the API and add it later if practical use shows there is a real need. However, I think the correct way to handle this should be to add use cases (and I think such use cases have been described in postings to this list) that such requirements are derived from and then in some ordered fashion discuss and decide between rtcweb and webrtc if those use cases/requirements should be prioritized for version 1 of the specs. Would this be an agreeable way to move forward? How should this be brought up with the rtcweb WG? Stefan
Received on Tuesday, 19 July 2011 06:11:22 UTC