W3C home > Mailing lists > Public > public-media-capture@w3.org > August 2013

Re: Object/method spellings for media stream recorder

From: Greg Billock <gbillock@google.com>
Date: Thu, 15 Aug 2013 15:47:14 -0700
Message-ID: <CAAxVY9eP69tSSpi3n=VA0UmhWq3NO+ws24HPCzNj7j7GLTtX4A@mail.gmail.com>
To: "Robert O'Callahan" <robert@ocallahan.org>
Cc: "public-media-capture@w3.org" <public-media-capture@w3.org>
On Thu, Aug 15, 2013 at 3:28 PM, Robert O'Callahan <robert@ocallahan.org>wrote:

> On Fri, Aug 16, 2013 at 3:55 AM, Greg Billock <gbillock@google.com> wrote:
>
>> I've started laying out the IDL for the recorder in Blink. Something I'm
>> finding is that it looks like the Mozilla implementation is using slightly
>> different names than the spec:
>>
>>
>> https://hg.mozilla.org/mozilla-central/file/a8daa428ccbc/dom/webidl/MediaRecorder.webidl
>>
>>
>> http://www.w3.org/TR/2013/WD-mediastream-recording-20130205/#MediaRecorderAPI
>>
>> Specifically, it looks like in Firefox the object is named
>> "MediaRecorder", and the method you use to begin recording is "start()".
>> The spec names these "MediaStreamRecorder" and "record()".
>>
>
> The spec name is "MediaRecorder". I prefer that, but it's not a big deal
> either way IMHO.
>

Oy. How did I mess that up? I guess reading the spec title too frequently.
Perhaps the title should change, but I'm content to use the name
'MediaRecorder'.



>
> Personally, I like "MediaStreamRecorder" due to the better consistency
>> with other WebRTC class names. I prefer "start()" to "record()" because of
>> "stop()".
>>
>
> I agree. Let's change the name in the spec :-).
>

sounds good. (I believe we're both referring to "record()" --> "start()"
right?)



>
> These aren't big points, but lets make sure we get the implementations and
>> spec matched up. Was there discussion on changing these names to the
>> Firefox vocabulary, and it hasn't made it to the spec yet? Or perhaps there
>> are other aliasing docs in Firefox that make the vocabulary the same as the
>> spec, and the IDL I linked is the result of correspondence to a previous
>> draft?
>>
>
> I'm not sure how we ended up in this state. We'll definitely fix it one
> way or another.
>
> Rob
> --
> Jtehsauts  tshaei dS,o n" Wohfy  Mdaon  yhoaus  eanuttehrotraiitny  eovni
> le atrhtohu gthot sf oirng iyvoeu rs ihnesa.r"t sS?o  Whhei csha iids  teoa
> stiheer :p atroa lsyazye,d  'mYaonu,r  "sGients  uapr,e  tfaokreg iyvoeunr,
> 'm aotr  atnod  sgaoy ,h o'mGee.t"  uTph eann dt hwea lmka'n?  gBoutt  uIp
> waanndt  wyeonut  thoo mken.o w  *
> *
>
Received on Thursday, 15 August 2013 22:47:41 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:26:18 UTC