- From: Adam Bergkvist <adam.bergkvist@ericsson.com>
- Date: Fri, 14 Dec 2012 10:41:35 +0100
- To: Dan Burnett <dburnett@voxeo.com>
- CC: "public-webrtc@w3.org" <public-webrtc@w3.org>
On 2012-12-13 14:59, Dan Burnett wrote: > I agree that we decided to add "id". I don't agree with removing > "label". My understanding from the f2f meeting was that we would end > up with both MediaStream and MediaStreamTrack objects having both > "id" (machine-generated) and "label" (human-generated) attributes. I remember us talking about the confusing regarding label meaning something on MediaStream and something else on MediaStramTrack, but I don't really recall the exact resolution. This edit was really a rename of what you refer to as the "machine-generated" identifier from "label" to "id" to align with MediaStreamTrack. We've never had a "human-generated" identifier on MediaStream so it hasn't been removed. :) I'm not really convinced we need a human settable identifier on MediaStream unless it's transported over a p2p connection (and we have a use-case for that). If you want to assign a custom label to a MediaStream on the local side you can simply add as many new properties to it as you like (myStream.label = "Web Cam & headset mic"; ). /Adam
Received on Friday, 14 December 2012 09:42:06 UTC