Consider request strategy when we schedule timeouts or retries #2482
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:
Currently, timeout and retrying filter uses an
HttpExecutionStrategy
from theExecutionContext
. However, on the requester side users can either use a different API that optimizes the pre-computed strategy or they can put a custom strategy per request.Modifications:
RetryingHttpRequesterFilter
, computealternativeTimerExecutor
based onHTTP_EXECUTION_STRATEGY_KEY
;TimeoutHttpRequesterFilter
, computeuseForTimeout
based onHTTP_EXECUTION_STRATEGY_KEY
;Result:
HttpExecutionStrategy
associated with the request is considered.