W3C home > Mailing lists > Public > public-webapps@w3.org > April to June 2014

Re: Why do keys() and values() on CacheList in ServiceWorkers not return promises

From: Jungkee Song <jungkees@gmail.com>
Date: Fri, 9 May 2014 13:35:09 +0900
Message-ID: <CAGwV++fX1SbGVD3euMc+qo_1D0LBn2wThP4Y_e75odyG-H3KGg@mail.gmail.com>
To: Boris Zbarsky <bzbarsky@mit.edu>
Cc: public-webapps <public-webapps@w3.org>
On May 9, 2014 1:16 PM, "Boris Zbarsky" <bzbarsky@mit.edu> wrote:
> In particular, given that get() wants to return a Promise, why do we want
values() to return a list of Cache objects synchronously?
> Similar for keys(): if has() needs to be async, then how can has() be

Exactly. both values() and keys() will be changed to async returning
Promises. I'll be working on that part of the ED shortly. It's a bit behind
the discussion going on in this ticket:

> -Boris
Received on Friday, 9 May 2014 04:35:37 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 18:14:24 UTC