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

Is it time to retire NPN? #856

Open
davidben opened this issue Mar 5, 2024 · 5 comments
Open

Is it time to retire NPN? #856

davidben opened this issue Mar 5, 2024 · 5 comments

Comments

@davidben
Copy link
Contributor

davidben commented Mar 5, 2024

The ALPN RFC is coming up on ten years old now. The oldest OpenSSL release with ALPN support, 1.0.2, came out January 2015, nine years ago. The oldest OpenSSL without ALPN, 1.0.1, went EOL in December 2016, now seven years ago.

Perhaps it's time to retire NPN support in Netty?

@normanmaurer
Copy link
Member

I think we could... Why you want to do this tho ?

@davidben
Copy link
Contributor Author

davidben commented Mar 6, 2024

I was just taking stock of who was still using NPN APIs to see how close we are to being able to remove them in BoringSSL. Quite a few callers remaining but I figured I'd file an issue and see if you all still need it.

@normanmaurer
Copy link
Member

I mean we support it in netty and I think we can't remove it without a major version release. Not sure its used in the wild tho

@davidben
Copy link
Contributor Author

I would hope that, by now, it's not load-bearing. But yeah, makes sense. Maybe time to mark deprecated if we think it's unused then?

@normanmaurer
Copy link
Member

@davidben yeah I think that is definitely something we should do... Will keep you posted

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants