- From: Stefan Håkansson LK <stefan.lk.hakansson@ericsson.com>
- Date: Tue, 13 Aug 2013 13:40:47 +0000
- To: "robert@ocallahan.org" <robert@ocallahan.org>
- CC: Martin Thomson <martin.thomson@gmail.com>, Greg Billock <gbillock@google.com>, "public-media-capture@w3.org" <public-media-capture@w3.org>
On 2013-07-31 06:58, Robert O'Callahan wrote: > On Wed, Jul 31, 2013 at 4:53 PM, Martin Thomson > <martin.thomson@gmail.com <mailto:martin.thomson@gmail.com>> wrote: > > On 31 July 2013 06:47, Robert O'Callahan <robert@ocallahan.org > <mailto: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? > > > No. What exists (as a document, I don't know about implementation status) is the Quota API. With it you could at least check how much memory that is available, and also request storage. https://dvcs.w3.org/hg/quota/raw-file/tip/Overview.html > > 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 Tuesday, 13 August 2013 13:41:13 UTC