Modify default channel factory to add support for 'null' schemes #448
+556
−116
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
|
Well I should probably read the issue completely first, before starting to implement it... |
ST-DDT
force-pushed
the
channelfactory/none
branch
from
b3f84d1
to
5dc1d77
Compare
|
Updated to fix conflicts, but I will delay this PR to the next milestone. |
ST-DDT
force-pushed
the
channelfactory/none
branch
from
5dc1d77
to
c00dc7a
Compare
Closed
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.
Fixes #419
TODO:
noneclient/channel address schemenoneclient/channel address (Optional)noneserver addressTBD:
Not sure about
noneornullyet.