Re: Synchronous versus asynchronous getSourceInfos

On Tue, Jun 4, 2013 at 2:11 PM, Martin Thomson <martin.thomson@gmail.com>wrote:

> On 4 June 2013 13:51, Justin Uberti <juberti@google.com> wrote:
> > While more grammatically correct, to me getSourceInfo reads like it's
> > getting the info about a particular source. How about getSources() (or
> > getUserSources) instead?
>
> getMediaSources, getSources, getUserMediaSources, or something like
> that is fine.  Paint the shed whatever colour you please.
>
>
If we keep the MediaStreamTrack scoping, MediaStreamTrack.getSources seems
like the least verbose construction.


>  > Also, as this makes getSourceInfos more like getUserMedia, is there a
> good
> > reason to have this as a static method on MediaStreamTrack as opposed to
> > Navigator, like getUserMedia? (I may have just missed this in the
> original
> > discussion)
>
> I value placement for establishing context.  Besides, Navigator
> already has plenty of responsibilities.
>

Consistency also has value. That said, this is also bikeshed territory.

Received on Tuesday, 4 June 2013 22:54:37 UTC