webpush-wg / webpush-protocol Public
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
Message collapsing #9
Comments
|
If we decide to pursue - To keep related changes together, the pull request should include the changes for the conditional DELETE of the message resource by the user agent. |
|
Defer to -01. |
|
Defer again. |
|
Deferred multiple times. Closing. Can be reopened if there is a requirement to support this scenario. |
|
Discussed in Yokohama: action on @martinthomson to generate a pull request that uses a string collapse key. That would allow the application server to operate in a stateless mode, something that the previous pull request would not allow. |
|
Just did a scan of the header fields that are already registered. The only one that is even a remote possibility for this purpose is SLUG. It looks like we might want to ask for another new one, current candidate: |
|
Topic sounds like a better option than reuse in this case. |
|
"Topic" may be a bit confusing, it is commonly used in pubsub. I don't know if pubsub uses a Topic header, but it may still confuse developers. |
|
So this is where it all went wrong :-( _TOPICS are NOT collapse keys!_ |
Need to do this once we have #3 and #6 are sorted out.
The text was updated successfully, but these errors were encountered: