Proposed changes to Reporting API

• From: Douglas Creager <dcreager@google.com>
• Date: Thu, 25 Jan 2018 09:52:25 -0500
• To: public-web-perf@w3.org
• Cc: juliatuttle@chromium.org
• Message-ID: <CAM0YUhBBmow5zZ6TQJ8iViPu3tgFgCbUwnVhzDEbu_ftRHZVgA@mail.gmail.com>

There are a couple of proposed changes to the Reporting API that I'd
like to get more feedback on.

The first is to reorganize all of the internal state so that
everything is grouped by the origin that the endpoints are attached
to.  Initial proposal is [1], draft spec update is [2].

[1] https://github.com/WICG/reporting/issues/64
[2] https://github.com/WICG/reporting/pull/67

The other is to decide whether sampling rates (which are part of the
current draft of NEL [3]) should be moved into Reporting, since they
would be useful to other Reporting-dependent specs.  Complicating the
issue is that NEL actually uses *two* sampling rates, which would
complicate any effort to move them into Reporting.  Open issue
tracking this discussion is [4].

[3] https://wicg.github.io/network-error-logging/#sampling-rates
[4] https://github.com/WICG/reporting/issues/45

Comments would be most welcome!

cheers
–doug

Received on Thursday, 25 January 2018 14:53:58 UTC