[Twisted-Python] Writing new transports / a tunnel Protocol

Jean-Paul Calderone exarkun at divmod.com
Sun Jul 27 08:38:44 EDT 2008

On Sun, 27 Jul 2008 02:28:37 -0700, Michael Carter <cartermichael at gmail.com> wrote:
> [snip]
>So my question is, what is the best way to take an implementation of this
>protocol and integrate it tightly with twisted's internals? It seems like I
>would need a new reactor implementation with a listenCTP function, for one.
>Of course, I wouldn't want to just inherit from the SelectReactor, because I
>want to be able to use Epoll (or others) as well.
>Please excuse my ignorance of twisted's architecture. I already have a
>prototype of this (see orbited 0.5.x) but I want my next release to
>integrate tightly with twisted's infrastructure instead of re-inventing an
>API on top.

You don't have to add a method to the reactor.  You can make a free
function which takes a reactor as an argument.


More information about the Twisted-Python mailing list