Skip to content
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

Add spec points around HTTP/2 support requirements for SDKs #5

Open
QuintinWillison opened this issue Sep 27, 2022 · 2 comments
Open
Labels
documentation Improvements or additions to documentation

Comments

@QuintinWillison
Copy link
Contributor

See this Slack thread (internal) where...

@lmars stated:

we support HTTP/2 on our primary endpoints, but not on our fallback endpoints. We should document that

and then:

client side we need to handle HTTP/2 in the expected way (try and use it, but then fallback to HTTP/1.1 if the server doesn't indicate it supports HTTP/2)

and @mattheworiordan stated:

I did explicitly ask about this in https://github.com/ably/ideas/issues/309#issuecomment-1096763108, but didn’t get a response. I assumed it was covered, but perhaps shouldn’t have assumed that. I think we need to be explicit on our spec. Could you propose a PR to address this?

@sync-by-unito
Copy link

sync-by-unito bot commented Oct 17, 2022

➤ Automation for Jira commented:

The link to the corresponding Jira issue is https://ably.atlassian.net/browse/SDK-2793

@mattheworiordan
Copy link
Member

Please note we need to also update our docs so that developers know our SDKs are HTTP/2 compatible.

@mattheworiordan mattheworiordan added the documentation Improvements or additions to documentation label Oct 9, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation
Development

No branches or pull requests

2 participants