W3C home > Mailing lists > Public > public-webappsec@w3.org > June 2013

Re: Fetching contexts

From: Anne van Kesteren <annevk@annevk.nl>
Date: Fri, 21 Jun 2013 10:37:30 +0900
Message-ID: <CADnb78g+oBn6ZkoZzkB7eeVLwcC+EL4=riEs28ZFQ0vjNQWRMA@mail.gmail.com>
To: Dirk Schulze <dschulze@adobe.com>
Cc: Boris Zbarsky <bzbarsky@mit.edu>, Gordon Hemsley <me@gphemsley.org>, Adam Barth <w3c@adambarth.com>, WebAppSec WG <public-webappsec@w3.org>
On Fri, Jun 21, 2013 at 2:28 AM, Dirk Schulze <dschulze@adobe.com> wrote:
> Can you elaborate more about the goal of this table? Is it a general overview as a help to create one spec "to rule them all", or hints/roadmaps for each different responsible specs? That would make it easier to contribute and review.

The idea is to decentralize CSP by having the context defined as part
of the API rather than CSP enumerating all APIs that are affected (and
how). CSP would presumably still exist to define the framework and
such.

Mainly it's a bad thing that you currently have to look at a large
number of specifications and combine them in your head to figure out
how fetching will behave for a particular feature.
http://annevankesteren.nl/2013/05/fetching-urls has a high-level
overview.


--
http://annevankesteren.nl/
Received on Friday, 21 June 2013 01:37:57 UTC

This archive was generated by hypermail 2.3.1 : Monday, 23 October 2017 14:54:02 UTC