We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Currently we have here:
AsyncDispatchInterface
SyncDispatchInterface
The Interface suffix looks a bit jarring to me, as in "of course they are interfaces, aren't they?".
Interface
What was the motivation for departing from AsyncDispatcher/SyncDispatcher?
AsyncDispatcher
SyncDispatcher
The text was updated successfully, but these errors were encountered:
Other potential naming, inspired by python-trio/hip#124 (comment), would be that of "transports", e.g...
AsyncHTTPTransport
SyncHTTPTransport
Sorry, something went wrong.
@florimondmanca What about these?
AsyncHTTPConnection
SyncHTTPConnection
Rolling with AsyncHTTPTransport/SyncHTTPTransport at the moment. Open to design discussions continuing on this, but that feels right for now.
No branches or pull requests
Currently we have here:
AsyncDispatchInterface
SyncDispatchInterface
The
Interface
suffix looks a bit jarring to me, as in "of course they are interfaces, aren't they?".What was the motivation for departing from
AsyncDispatcher
/SyncDispatcher
?The text was updated successfully, but these errors were encountered: