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

Make ProtocolSslContextSpec generic #3150

Merged
merged 1 commit into from Apr 16, 2024
Merged

Conversation

violetagg
Copy link
Member

  • QuicSslContextBuilder does not extend SslContextBuilder.
  • Add Http3SslContextSpec, similar to Http2SslContextSpec and Http11SslContextSpec.

Related to #1531

- QuicSslContextBuilder does not extend SslContextBuilder.
- Add Http3SslContextSpec, similar to Http2SslContextSpec and Http11SslContextSpec.

Related to #1531
@violetagg violetagg added the type/enhancement A general enhancement label Apr 11, 2024
@violetagg violetagg added this to the 1.2.0-M2 milestone Apr 11, 2024
@violetagg violetagg requested review from chemicL and a team April 11, 2024 12:10
Copy link
Member

@pderop pderop left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

+1

as discussed, maybe we can deprecate the old sslContext(ProtocolSslContextSpec spec)signature in SslProvider.SslContextSpec.
Something like:

		/**
		 * SslContext builder that provides, specific for the protocol, default configuration
		 * e.g. {@link DefaultSslContextSpec}, {@link TcpSslContextSpec} etc.
		 * The default configuration is applied before any other custom configuration.
		 *
		 * @param spec SslContext builder that provides, specific for the protocol, default configuration
		 * @return {@literal this}
		 * @since 1.0.6
		 * @deprecated as of 1.2.0. Prefer using {@link #sslContext(SslProvider.GenericSslContextSpec)}  
		 * This method will be removed in version 1.3.0.
		 */
		@Deprecated
		Builder sslContext(ProtocolSslContextSpec spec);

@violetagg
Copy link
Member Author

+1

as discussed, maybe we can deprecate the old sslContext(ProtocolSslContextSpec spec)signature in SslProvider.SslContextSpec. Something like:

		/**
		 * SslContext builder that provides, specific for the protocol, default configuration
		 * e.g. {@link DefaultSslContextSpec}, {@link TcpSslContextSpec} etc.
		 * The default configuration is applied before any other custom configuration.
		 *
		 * @param spec SslContext builder that provides, specific for the protocol, default configuration
		 * @return {@literal this}
		 * @since 1.0.6
		 * @deprecated as of 1.2.0. Prefer using {@link #sslContext(SslProvider.GenericSslContextSpec)}  
		 * This method will be removed in version 1.3.0.
		 */
		@Deprecated
		Builder sslContext(ProtocolSslContextSpec spec);

ok I will deprecate with a separate PR

@violetagg violetagg merged commit 6d0c24d into main Apr 16, 2024
14 checks passed
@violetagg violetagg deleted the http3-ssl-context-builder branch April 16, 2024 06:15
violetagg added a commit that referenced this pull request Apr 16, 2024
Netty Quic Codec and HTTP3 Codec are not migrated to Netty5
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type/enhancement A general enhancement
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants