Re: [Webpush] Use Case related to subscription sets

[Brian Raymor <[e-mail]>]

> An explicit link between subscriptions isn't that hard to do.  I've
> created a pull request that illustrates how simple it would be to
> accommodate Hervé's request.

> https://github.com/webpush-wg/webpush-protocol/pull/67

Thanks for creating the pull request, Martin. I've added specific comments there.

The question is whether the WG prefers "user agent decides" - which is the case
where the push service advertises the availability of sets in its response to
the first subscription request and the user agent can then decide whether to
pass the push:set with subsequent subscription requests for aggregation. This is
definitely a very flexible approach although with a  few more moving parts.

In previous discussions, one of the concerns about "user agent decides" is what
happens if a push service strongly wants to require aggregation, but the user agent
fails to include the advertised push:set with its subsequent subscription requests?
This was one of the motivations for the current approach of "push service decides".

Perhaps the combination of "user agent decides" with "push service *encourages*"
by limiting concurrent HTTP/2 streams is the potential compromise.