Can we merge twotp into Twisted proper?

[oubiwann]

Thomas' work on twotp would be a general asset to Twisted users, providing interoperation with Erlang code/projects. Erlang is well-established as a standard tool in the world of concurrent programming, so this seems less of a risk than it might have been 4 years ago.

What's more, ticket #5565 could greatly benefit from this work, making our lives easier in the process.

What would it take to make this happen?

[glyph]

Replying to oubiwann:

Thomas' work on twotp would be a general asset to Twisted users, providing interoperation with Erlang code/projects. Erlang is well-established as a standard tool in the world of concurrent programming, so this seems less of a risk than it might have been 4 years ago.

No argument here.

What's more, ticket #5565 could greatly benefit from this work, making our lives easier in the process.

Hrm. I'm not sure I'm on board with that, though. Let's not conflate the wire protocol and the message system. I would imagine that AMP would be a more suitable initial transport / framing protocol for #5565, and OTP could be added later, for interoperability with erlang nodes, not as a basis for the system itself. Someone with more direct knowledge of OTP could of course feel free to educate me about its awesome properties for such systems, though.

What would it take to make this happen?

A patch, tests, documentation; the usual stuff :). Not much more, I'd guess.

[oubiwann]

Awesome, glyph, thanks. And, yeah wrt ticket #5565, AMP was discussed as the primary target, with Erlang being a nice-to-have (irc log here:  http://www.twistedmatrix.com/users/oubiwann/actorModel/ircLogs/actor-model-twisted-irc-meeting-02.txt).

I should have been more clear in my description of this bug.

[exarkun]

Are people using twotp? Are people who should be using it not using it because it isn't part of Twisted?