[HTTPSchedulableRequest] EventLoop preferences#415
Merged
Uh oh!
There was an error while loading. Please reload this page.
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters. Learn more about bidirectional Unicode characters
fabianfett changed the title fabianfett changed the title 
glbrntt approved these changes Sep 7, 2021
Lukasa approved these changes Sep 7, 2021
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment
3 participants
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 we have a
var eventLoopPreference: HTTPClient.EventLoopPreferencerequirement onHTTPSchedulableRequest. Sadly in the.indifferentcase theHTTPSchedulableRequestdoes not expose an eventLoop to create a connection on.Changes
var eventLoopPreference: HTTPClient.EventLoopPreferenceon theHTTPSchedulableRequestwithvar requiredEventLoop: EventLoop?andvar preferredEventLoop: EventLoopResult
We don't need to hold an
EventLoopGroupin theConnectionPoolStateMachine.