2011/webrtc/editor getusermedia.html,1.9,1.10

Update of /sources/public/2011/webrtc/editor
In directory hutz:/tmp/cvs-serv27945/webrtc/editor

Modified Files:
	getusermedia.html 
Log Message:
Add additional clarifications to impl. suggestions


Index: getusermedia.html
===================================================================
RCS file: /sources/public/2011/webrtc/editor/getusermedia.html,v
retrieving revision 1.9
retrieving revision 1.10
diff -u -d -r1.9 -r1.10
--- getusermedia.html	6 Jun 2012 04:31:08 -0000	1.9
+++ getusermedia.html	7 Jun 2012 06:20:58 -0000	1.10
@@ -1351,24 +1351,34 @@
           callback provided by the web page. Subsequent calls to
           <a href="#dom-navigator-getusermedia">getUserMedia()</a> (in this
           page or any other) should treat the resource that was previously
-          allocated as busy, and disallow access to the stream from that source
-          unless otherwise indicated by the user.
+          allocated, as well as resources held by other applications, as busy.
+          Resources marked as busy should not be provided as sources to the
+          current web page, unless specified by the user.
           </p>
 
           <p>
           It is suggested that in the permission grant dialog or device
           selection interace (if one is present), the user be allowed to select
           any available hardware as a source for the stream requested
-          by the page, in addition to the ability to substitute a video or
-          audio source with local files and other media. It is also suggested
-          that the user be shown all resources that are currently busy as a
-          result of prior calls
+          by the page (provided the resource is able to fulfil mandatory
+          constraints, if any were specified), in addition to the ability to
+          substitute a video or audio source with local files and other media.
+          A file picker may be used to provide this functionality to the user.
+          </p>
+
+          <p>
+          It is also suggested that the user be shown all resources that are
+          currently busy as a result of prior calls
           to <a href="#dom-navigator-getusermedia">getUserMedia()</a>
           (in this page or any other page that is still alive), and be allowed
           to terminate that stream and utilize the resource for the current page
-          instead. If the user chooses this option, the <a>onended</a> event
-          must be raised on the stream provided to page whose session was
-          terminated.
+          instead. If possible in the current operating environment, it is also
+          suggested that resources currently held by other applications be
+          presented and treated in the same manner. If the user chooses this
+          option, the track corresponding to the resource that
+          was provided to the page whose stream was affected must be removed.
+          Additionally, if removing a track in this manner causes the stream to
+          contain no more tracks, the <a>onended</a> event must be raised on it.
           </p>
         </subsection>

Received on Thursday, 7 June 2012 06:21:07 UTC