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

Re: Communicating memory pressure in mediastream recording

From: Robert O'Callahan <robert@ocallahan.org>
Date: Wed, 31 Jul 2013 16:56:42 +1200
Message-ID: <CAOp6jLbwrezinE9tMFW-rannYqhOidiD9J2=h-Zi5i+=X-3MxA@mail.gmail.com>
To: Martin Thomson <martin.thomson@gmail.com>
Cc: Greg Billock <gbillock@google.com>, "public-media-capture@w3.org" <public-media-capture@w3.org>
On Wed, Jul 31, 2013 at 4:53 PM, Martin Thomson <martin.thomson@gmail.com>wrote:

> On 31 July 2013 06:47, Robert O'Callahan <robert@ocallahan.org> wrote:
> >> Is there an API surface that might support this already?  Or would
> >> this require that things just sort of stop working in the interim?
> >
> > I'm not sure what you mean.
> Is there some existing way that a browser might communicate to an app
> that there is memory/resource pressure, in such a way that an app
> might infer the reasons for errors that might arise in that state?


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 Wednesday, 31 July 2013 04:57:08 UTC

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