You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
How difficult would it be to make the request builder sendable, so a user of the lib could create a request builder and then send it to a helper task while it blocks on network io?
The text was updated successfully, but these errors were encountered:
I'm not sure about difficulty, but it must happen. It's a goal that you can
have multiple requests running at the same time, but current design impedes
that.
How difficult would it be to make the request builder sendable, so a user
of the lib could create a request builder and then send it to a helper task
while it blocks on network io?
—
Reply to this email directly or view it on GitHub #254.
Connector::connect already used &self, and so would require
synchronization to be handled per connector anyway. Adding Sync to the
Client allows users to setup config for a Client once, such as using a
single connection Pool, and then making requests across multiple
threads.
Closes#254
BREAKING CHANGE: Connectors and Protocols passed to the `Client` must
now also have a `Sync` bounds, but this shouldn't break default usage.
How difficult would it be to make the request builder sendable, so a user of the lib could create a request builder and then send it to a helper task while it blocks on network io?
The text was updated successfully, but these errors were encountered: