W3C home > Mailing lists > Public > public-media-capture@w3.org > December 2011

RE: Thoughts on converging MediaStream and Stream objects

From: Travis Leithead <travis.leithead@microsoft.com>
Date: Thu, 8 Dec 2011 18:42:29 +0000
To: Dominique Hazael-Massieux <dom@w3.org>
CC: "public-media-capture@w3.org" <public-media-capture@w3.org>
Message-ID: <9768D477C67135458BF978A45BCF9B38381C52CF@TK5EX14MBXW602.wingroup.windeploy.ntdev.microsoft.com>
>-----Original Message-----
>From: Dominique Hazael-Massieux [mailto:dom@w3.org]
>
>To the risk of starting a bikeshedding discussion, is there a way to
>find a different name for one or the other of the two interfaces, if
>they can't be linked by an inheritance logic? It's very likely to cause
>a lot of confusion if Stream and MediaStream aren't actually strongly
>related.
>
>Would MediaSource work for instance? MediaConduit? MediaChannel?
>
>Or maybe Stream should be StreamedBlob?

Agree that this is a bit confusing, especially because the WebRTC spec calls the MediaStream interface the "Stream API". If the editors want to make a name change now, I’m fine that it, but I don't have any specific preference.
Received on Thursday, 8 December 2011 18:43:07 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 16:14:58 GMT