Ensure host server waits with forwarding requests to worker #2754
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 PR moves the state of the host server into the
AppContextclass. (I say "state" but it's just the worker and whether the backend is ready.) This makes it easier to control access to the worker. I made the worker a private field and give it out via 2 methods:get_workerandget_worker_unmanaged. The difference between these two is thatget_workerwill wait until the backend is fully ready, whileget_worker_unmanagedwill not. So code that wants to use the worker has to declare whether it wants a ready worker or a worker in any state.This fixes the loading issue we talked about here.