W3C home > Mailing lists > Public > public-media-capture@w3.org > February 2014

Re: Constraints and MediaRecorder

From: Robert O'Callahan <robert@ocallahan.org>
Date: Tue, 11 Feb 2014 09:26:31 +1300
Message-ID: <CAOp6jLYZVQeW6SYtD+O9otvpF-GQVoMQZpzRvBEQrxFLpAf+yA@mail.gmail.com>
To: cowwoc <cowwoc@bbs.darktech.org>
Cc: "public-media-capture@w3.org" <public-media-capture@w3.org>
On Tue, Feb 11, 2014 at 3:43 AM, cowwoc <cowwoc@bbs.darktech.org> wrote:

>  Surely there is room for improving the API's usability without needing
> new use-cases? There are plenty of ways to address our current set of
> use-cases. That doesn't mean that we should remain fixated on a particular
> API if a better design comes along.

It's true that there are sometimes use-cases which are possible but not
easy to address with existing APIs, and it's worth adding new APIs to make
them easy. But that's not the situation EKR is describing, AFAICT.

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 Monday, 10 February 2014 20:27:01 UTC

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