Introduce client pool #83
Closed
Conversation
This file contains 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
The client pool is used to create the desired number of client instances which are accessible in a thread safe fashion.
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.
The client pool is used to create the desired number of client instances which are accessible in a thread safe fashion.
Different threads can assign a task to the pool, by calling the
::runmethod; this is a method that accepts a callback with a signature<Ret(client *)>whereRetis any type. Inside that callback, the provided client is accessed in a thread safe manner.Selection of an idle client from the pool is done in a round robin fashion and will wait to find an idle "worker" when all clients in the pool are busy.
Also added an example.