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
implement the transport plugins using the twisted/zope IPlugin interface #26
Conversation
Conflicts: foolscap/pb.py
Conflicts: setup.py src/foolscap/connection_plugins.py
here we also reuse the proxy endpoint for additional socks connections with this endpoint instance
…t failed here we change the SOCKS5 plugin class to raise PluginDependencyNotLoaded in it's constructor if txsocksx previously failed to import
here we also make the setup.py install the twisted plugins
I think we've decided to not use automatic plugin discovery for this, but to oblige applications to install whatever connection handlers they want to enable (since most handlers will require configuration, and that configuration has to come from somewhere user-facing, and neither foolscap nor plugins have anything particularly user-facing). So I'm gonna say we shouldn't land this one. What do you think? |
closing this as WONTFIX, we're going to leave applications (and not foolscap) responsible for discovering/configuring/installing connection handlers. thanks! |
No description provided.