This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 22260 - Give guidance on defining MediaStream consumers
Summary: Give guidance on defining MediaStream consumers
Status: RESOLVED LATER
Alias: None
Product: WebRTC Working Group
Classification: Unclassified
Component: Media Capture and Streams (show other bugs)
Version: unspecified
Hardware: PC Linux
: P2 normal
Target Milestone: ---
Assignee: public-media-capture@w3.org
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-06-04 11:57 UTC by Dominique Hazael-Massieux
Modified: 2014-04-03 13:08 UTC (History)
3 users (show)

See Also:

Attachments

Description Dominique Hazael-Massieux 2013-06-04 11:57:48 UTC 
The spec has some (arguably already limited) guidance on a specific MediaStream consumer, the HTML Media elements.

It should probably define more generally what it means to define a MediaStream consumer; in addition to Media elements and PeerConnection, there is already AudioContext.createMediaStreamSource(), and I can imagine that Media Source Extension should define at some point a SourceBuffer.appendMediaStream() method.
Comment 1 Adam Bergkvist 2013-10-02 10:50:20 UTC 
We have a paragraph [1] that briefly describes what a MediaStream consumer is. That paragraph is followed by a note that mentions that consumers need to handle tracks coming and going. Perhaps the content of that note should be the first bullet in a list of requirements that are put on consumers.

[1] http://dev.w3.org/2011/webrtc/editor/getusermedia.html#dfn-consumer
Comment 2 Dominique Hazael-Massieux 2014-04-03 13:05:15 UTC 
FWIW, while I still think this will be needed, this is more of a mid term issue, so it would be fine to close this bug as "resolved later".
Comment 3 Stefan Hakansson LK 2014-04-03 13:08:08 UTC 
Following Dom's recommendation.