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
[alpn] Remove grpc-exp experimental ALPN protocol. #34876
[alpn] Remove grpc-exp experimental ALPN protocol. #34876
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, one comment if you want to make the change bigger
@@ -25,7 +25,7 @@ | |||
#include "src/core/lib/gpr/useful.h" | |||
|
|||
// in order of preference | |||
static const char* const supported_versions[] = {"grpc-exp", "h2"}; | |||
static const char* const supported_versions[] = {"h2"}; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we plan to have any other supported versions? Otherwise I wonder if it's worth it to just remove this complexity altogether and have a non-arr const value for h2
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm planning a follow-up PR to clean up this file (some of the APIs, e.g. grpc_chttp2_get_alpn_version_index
, are now unused). Do you mind if we defer this to the cleanup PR?
@markdroth @ejona86 Could one of you confirm that this should be safe? The |
There's talk in the http2 community of introducing a new version of the
http2 protocol (which would get a new string) to properly deal with rapid
reset.
We should probably keep this machinery around for that.
…On Fri, Nov 3, 2023, 3:33 PM Matthew Stevenson ***@***.***> wrote:
@markdroth <https://github.com/markdroth> @ejona86
<https://github.com/ejona86> Could one of you confirm that this should be
safe? The grpc-exp has already been removed from Go and Java, but I'd
like to confirm that there are no edge cases for the C-core or wrapped
languages that are still dependent on this ALPN protocol.
—
Reply to this email directly, view it on GitHub
<#34876 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/ACNG45K5VK7UXQSWYMBGGILYCVWMJAVCNFSM6AAAAAA6424XRCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTOOJTGE4TGOJUHA>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
@markdroth or @ejona86 Could one of you confirm that this should be safe, as far as you're aware? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I believe this to be safe
Thanks Eric! Will merge when the repo is unlocked. |
This fixes #21619. This experimental ALPN protocol has already been removed from the other gRPC stacks.