WIP: separate interface into immutable and mutable #5
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.
Rough sketch of
HttpRequestInfo
separation discussed on #4 (comment) .Change summary is the following:
HttpRequestInfo
andMutableHttpRequestInfo
, the latter is for mutating headersSpringHttpRequestInfo::trySetHeader
receives only acceptable header names, the function should not be accept some headersIs the design good? Please send me a feedback.