Make WebSocketDecoderConfig not final #13601
Open
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.
Motivation:
WebSocketDecoderConfig is currently final, which means that some aspects (eg
maxFramePayloadLength
) cannot be changed as a result of - for example - anAuthorization
header sent with the initial handshake, or with some sort of initial "login" websocket message.I can't see any reason why this field in particular has to be final; it's not like the value for one received frame has to be identical to a frame received for a different message.
Modification:
I've made the class non-final so it can be extended, but - because there is a builder class - I've made the new zero-argument constructor protected, so it can only be called by someone explicitly subclassing this class.
Result:
Addresses #13600