-
Notifications
You must be signed in to change notification settings - Fork 36
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
extensions-negotiation
definition
#112
base: main
Are you sure you want to change the base?
Conversation
concept ack |
@Fi3 @TheBlueMatt @jakubtrnka this PR is ready for review |
@Fi3 just a reminder to approve this, as we agreed during yesterday's call |
c6f28d9
to
590457b
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm just curious—Is the primary reason for not adding another field to the setup connection message and instead introducing an entirely new message exchange to ensure that, in case of an error (such as one party not supporting a particular extension), the connection remains open? This way, the client can modify the extension set and resend the extension request rather than having the connection closed.
590457b
to
6fc0770
Compare
This PR defines extension n.1 which allows for any implementation to support future extensions in a clean and scalable way.
Close #111