Mark some methods as protected to make it easier to write own SslCont… #10953
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…ext implementations Motivation: We should expose some methods as protected to make it easier to write custom SslContext implementations. This will be reused by the code for netty/netty-incubator-codec-quic#97 Modifications: - Add protected to some static methods which are useful for sub-classes - Remove some unused methods - Move *Wrapper classes to util package and make these public Result: Easier to write custom SslContext implementations
chrisvest
reviewed
Jan 21, 2021
chrisvest
approved these changes
Jan 21, 2021
normanmaurer
added a commit
that referenced
this pull request
Jan 21, 2021
…ext implementations (#10953) Motivation: We should expose some methods as protected to make it easier to write custom SslContext implementations. This will be reused by the code for netty/netty-incubator-codec-quic#97 Modifications: - Add protected to some static methods which are useful for sub-classes - Remove some unused methods - Move *Wrapper classes to util package and make these public Result: Easier to write custom SslContext implementations
ZzxyNn
pushed a commit
to ZzxyNn/netty
that referenced
this pull request
Jan 29, 2021
…ext implementations (netty#10953) Motivation: We should expose some methods as protected to make it easier to write custom SslContext implementations. This will be reused by the code for netty/netty-incubator-codec-quic#97 Modifications: - Add protected to some static methods which are useful for sub-classes - Remove some unused methods - Move *Wrapper classes to util package and make these public Result: Easier to write custom SslContext implementations
raidyue
pushed a commit
to raidyue/netty
that referenced
this pull request
Jul 8, 2022
…ext implementations (netty#10953) Motivation: We should expose some methods as protected to make it easier to write custom SslContext implementations. This will be reused by the code for netty/netty-incubator-codec-quic#97 Modifications: - Add protected to some static methods which are useful for sub-classes - Remove some unused methods - Move *Wrapper classes to util package and make these public Result: Easier to write custom SslContext implementations
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
…ext implementations
Motivation:
We should expose some methods as protected to make it easier to write custom SslContext implementations.
This will be reused by the code for netty/netty-incubator-codec-quic#97
Modifications:
Result:
Easier to write custom SslContext implementations