Re: [w3c/push-api] Consider including `supportedContentEncodings` in the `PushSubscription` serializer (#277)

Making it separate in the PushSubscription won't solve the issue of upgrades/rollback though, right ? App servers need to know what content encoding is supported by the browser for each subscription, so they have to store this info alongside the subscription in their database.
On the contrary, if the `supportedContentEncodings` becomes part of `PushSubscription`, app servers won't have any work to do for the transition (for libraries that uses the JSON `PushSubscription` as an entry point).

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/push-api/issues/277#issuecomment-314825558