[Twisted-Python] More coil TODOs
== Make ports visible == Currently, tcp/udp/ssl are treated as collections of protocol factories. I am going to change this to collections of Ports, so that you can configure interfaces to listen on, context factories for SSL, etc. The protocol factory will just be another attribute. This should have no effect on people who are coiling their apps. == Make old TAPs work == The refactor broke old taps - they can no longer be loaded since they refer to non-existence classes in twisted.internet.app. This can probably be easily solved (make a dummy PortsCollection class and delete the attributes of the loaded application that refer to it.)
On Fri, 2002-03-29 at 04:45, Itamar Shtull-Trauring wrote:
== Make ports visible == Currently, tcp/udp/ssl are treated as collections of protocol factories. I am going to change this to collections of Ports, so that you can configure interfaces to listen on, context factories for SSL, etc. The protocol factory will just be another attribute.
This should have no effect on people who are coiling their apps.
Does this affect the API? I don't want to have listenTCP et. al. taking something other than a factory (might as well go back to addPort, then).
== Make old TAPs work == The refactor broke old taps - they can no longer be loaded since they refer to non-existence classes in twisted.internet.app.
This can probably be easily solved (make a dummy PortsCollection class and delete the attributes of the loaded application that refer to it.)
Please consider this *really* high-priority; I hate to do releases where previous-version TAP loading is broken. -- | <`'> | Glyph Lefkowitz: Travelling Sorcerer | | < _/ > | Lead Developer, the Twisted project | | < ___/ > | http://www.twistedmatrix.com |
Glyph Lefkowitz wrote:
This should have no effect on people who are coiling their apps.
Does this affect the API? I don't want to have listenTCP et. al. taking something other than a factory (might as well go back to addPort, then).
No, it won't. I'd just be changing the Collections attached to an Application by the Configurator. This is why it's good that coil is no seperate - no need to mess with classes. And no TAP backwards compatability issues either ;)
participants (2)
-
Glyph Lefkowitz -
Itamar Shtull-Trauring