You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
Endpoint clients are a list, but making them a map from client origin to that client would make updates and deletes faster.
Cache endpoints are a list, but making them a map from endpoint URL to that endpoint would make updates and deletes faster.
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).
The text was updated successfully, but these errors were encountered:
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.
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:
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).
The text was updated successfully, but these errors were encountered: