ConnectionFactory-level filters can not migrate to new API of #1956 #2089
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:
In #1956
StreamingHttpRequester
defines a new methodrequest(StreamingHttpRequest)
.AbstractStreamingHttpConnection
onlyimplements the deprecated method that also takes an
HttpExecutionStrategy
. Users who apply a filter throughConnectionFactory
seeUnsupportedOperationException
. Also, if theyhave 2+ filters applied through
ConnectionFactory
, they can not mixdeprecated and new API.
Modifications:
AbstractStreamingHttpConnection#request(StreamingHttpRequest)
;NewToDeprecatedFilter
to beConnectionFactoryFilter
too;NewToDeprecatedFilter
when users invokeappendConnectionFactoryFilter
;appendConnectionFactoryFilter
inMixedFiltersTest
;Result:
Users who apply request/response filters through
ConnectionFactory
can migrate from deprecated to new
request(StreamingHttpRequest)
API.