-
Notifications
You must be signed in to change notification settings - Fork 1k
Threadpool Refactor #1168
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
Threadpool Refactor #1168
Conversation
eba6332 to
a6c8fca
Compare
|
Hi, I would like to suggest use a third thread pool implementation: https://github.com/bshoshany/thread-pool |
Agree. If I'm unable to fix the macos socket issues, I will most likely switch and experiment with that one. Good point. |
|
The ASIO thread pool is also a good choice. |
a15f238 to
bba1f7c
Compare
e018f5e to
e31ba2d
Compare
Yes! With ASIO threadpool we could get an awaitable Get/Post and use that within a boost coroutine. That would be nice to have. |
Refactors
cpr::ThreadPoolto get rid of all those deadlocks and overly complex code making it at least a bit simpler.Fixes:
Docs:
cpr::ThreadPoolDocumentation docs#54