Set connection status to ERROR when closed due to protocol error (#126) #127
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.
Set connection status to ERROR when closed due to protocol error
Motivation:
Addresses #126
Modifications:
DuplexConnection#close
to accept an optional error indicating that the connection is being closed due to that errorRSocketMachine
to pass protocol-level connection errors to closeResult:
Protocol-level errors will forward the error through the new
error
parameter inDuplexConnection#close
, resulting inERROR
status instead ofCLOSED