Re: Communicating memory pressure in mediastream recording from Martin Thomson on 2013-07-31 (public-media-capture@w3.org from July 2013)

From: Martin Thomson <martin.thomson@gmail.com>
Date: Wed, 31 Jul 2013 06:53:04 +0200
To: "Robert O'Callahan" <robert@ocallahan.org>
Cc: Greg Billock <gbillock@google.com>, "public-media-capture@w3.org" <public-media-capture@w3.org>
Message-ID: <CABkgnnXBBbybMHF7z1dkCGAyH6idaXpcfWf_S8FnD-E9f8pQ6g@mail.gmail.com>

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?

Received on Wednesday, 31 July 2013 04:53:31 UTC