- From: Domenic Denicola <notifications@github.com>
- Date: Tue, 01 May 2018 14:56:54 -0700
- To: w3ctag/design-reviews <design-reviews@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
- Message-ID: <w3ctag/design-reviews/issues/278@github.com>
Hello TAG! I'm requesting a TAG review of: - Name: Async local storage - Specification URL: https://domenic.github.io/async-local-storage/ - Explainer, Requirements Doc, or Example code: https://github.com/domenic/async-local-storage/blob/master/README.md - Tests: in progress at https://github.com/domenic/async-local-storage/tree/master/prototype/tests - Primary contacts: @domenic Further details (optional): - I have read and filled out the [Self-Review Questionnare on Security and Privacy](https://www.w3.org/TR/security-privacy-questionnaire/). The assessment is "No" to all, with the following additional notes: - "Does this specification introduce new state for an origin that persists across browsing sessions?" No _new_ state is introduced. However, the existing mechanism of IndexedDB is layered on top of and reused. - "Does this specification persist data to a user’s local device?" Yes, using IndexedDB's mechanisms. It follows IndexedDB in its interaction with "clear browsing data" and similar. - Unlike IndexedDB, this feature specifically requires a secure context, as it is a new storage API. - I have reviewed the TAG's [API Design Principles](https://w3ctag.github.io/design-principles/) You should also know that... This is designed as a [layered API](https://github.com/drufball/layered-apis); see #276 for that review request. We'd prefer the TAG provide feedback as (please select one): - open issues in our Github repo for each point of feedback -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/w3ctag/design-reviews/issues/278
Received on Tuesday, 1 May 2018 21:57:16 UTC