-
Notifications
You must be signed in to change notification settings - Fork 139
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Rationalise TLSConfiguration construction.
Motivation: Currently whenever we add new config to TLSConfiguration, we add a new static factory function that needs to provide the field. This is because we currently allow configuration primarily by way of initializers. This is increasingly not scaling, leading to a proliferation of almost identical static factory functions. We can replace this proliferation by having only "default" constructions that default basically everything, and then having users use getters/setters to initialize things. This also works well when we have multiple ways of interacting with config, e.g. with the various cipher suite operations. Modifications: - Deprecate all existing factory functions. - Replace with two: forClient() and forServer(certificateChain:privateKey:). These configure only the mandatory things for each mode. - Replace all uses of the deprecated initializers with the new ones, configuring fields manually as needed. Result: More consistent configuration objects.
- Loading branch information
Showing
16 changed files
with
571 additions
and
363 deletions.
There are no files selected for viewing
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
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
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
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
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
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
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
Oops, something went wrong.