[Twisted-Python] Using IConnector
kwaker at uch.net
Tue Feb 18 22:09:10 EST 2003
Wednesday, February 19, 2003, 4:10:47 AM, you wrote:
>> Ok, well, I can't speak for this part of twisted.. but I *think* the
>> proper way would be to make it a Transport, not a Protocol. For
>> example, if you were behind a stupid firewall and you wanted to make
>> connections to another host outside of the firewall, you would have to
>> refactor a lot less code if it could just be a transport.
>> Just an idea, again, I'm not an authority on this in any way.
CA> I'm not sure why I didn't think of this earlier, but yes, it does
CA> sound like a transport is the way to go -- it's exactly the kind of
CA> thing that the transport/protocol separation was done for.
Ok, I agree that transport sounds better, will refactor later today.
When should I attach new transport (instead of standard TCP) and how
client code, that connects to some host using SOCKS, will look like?
Dmitry mailto:kwaker at uch.net
More information about the Twisted-Python