Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Specify better data structures #14

Closed
juliatuttle opened this issue Aug 8, 2016 · 1 comment
Closed

Specify better data structures #14

juliatuttle opened this issue Aug 8, 2016 · 1 comment
Labels
report-delivery Covers the core delivery of reports via HTTP

Comments

@juliatuttle
Copy link
Contributor

There are places in the spec where we specify a list, but then effectively use the data structure as a map or a set. For example:

  1. Endpoint clients are a list, but making them a map from client origin to that client would make updates and deletes faster.
  2. Cache endpoints are a list, but making them a map from endpoint URL to that endpoint would make updates and deletes faster.
  3. Cache reports are a list, but making them a set would make random dequeues faster.

Using maps in cases 1 and 2 would also make it clearer that we only expect to have one endpoint per endpoint URL, and one client per (endpoint, origin).

@dcreager dcreager added the report-delivery Covers the core delivery of reports via HTTP label May 22, 2018
@clelland
Copy link
Contributor

Closing this as very stale; most of the infrstructure has been rewritten in terms of different data structures in the meantime, with the new reporting spec.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
report-delivery Covers the core delivery of reports via HTTP
Projects
None yet
Development

No branches or pull requests

3 participants