-
Notifications
You must be signed in to change notification settings - Fork 16
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
Subscription parameters #123
Comments
This was referenced Aug 23, 2023
Ah, @CxRes just wrote up a great list of subscription parameters for consideration here: #124 (comment)! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The spec provides a lot of flexibility in how servers return subscription data:
We would like clients to be able to specify how they'd like this data.
We have left room in the
Subscribe: <parameters>
header to specify these parameters. This issue is a spcae to design the parameters spec. What options should exist in there? How should they be specified?See the Structured Headers rfc8941 for reference on how to structure header values in HTTP.
This issue consolidates discussions from: #80 (
keep-alive
), #92 (rebase mode), #101 (rebase mode), and #115 (rate & format of updates), and should be consider the discussion in #105.The text was updated successfully, but these errors were encountered: