LeakyBucketExecutionPolicy support for requests context #672
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.
This is a non breaking change.
A new optional parameter
getRequestContext
can be supplied when constructing aLeakyBucketExecutionPolicy
.It serves to indicate whether the current context is
Foreground
orBackground
. The policy will prioritize foreground requests and run them first.For example, if a user is waiting on the request (loading a page showing response results for example), you would want to prioritize this request over competing requests that might be running in the background (to run some jobs for example).
(In this scenario, you could for example inspect if there is an ambient HttpContext to determine whether the request is Foreground or Background)