[Twisted-Python] Twisted+M2Crypto patch

Christopher Armstrong radeex at gmail.com
Wed Aug 11 18:01:19 MDT 2004

On Wed, 11 Aug 2004 18:21:08 -0400, J C Lawrence <claw at kanga.nu> wrote:
> On Wed, 11 Aug 2004 17:50:13 -0400
> Glyph Lefkowitz <glyph at divmod.com> wrote:
> > On Wed, 2004-08-11 at 17:40, James Y Knight wrote:
> > So, PyOpenSSL should plug into the reactor as a transport, but all
> > other (saner) Python SSL implementations ought to plug in as a
> > protocol.
> Ahem.  SSL in this parlance is just a TCP connection form with more
> dependencies (keys) failure modes (negotiation failures).  The protocol
> that flows over the SSL/TCP connection is arbitrary (eg HTTP, telnet,
> SMTP, etc).

Your tone indicates contradiction, but in fact, it's not: As far as
structuring SSL into Twisted goes, the logical way to do it is to
implement it as a Protocol (note the capital "P") and then use that
Protocol as a transport.  Glyph was referring to this, not any
abstract sense of where SSL fits into the 7-layer burrito^WOSI model

 Twisted | Christopher Armstrong: International Man of Twistery
  Radix  |          Release Manager,  Twisted Project
---------+            http://radix.twistedmatrix.com

More information about the Twisted-Python mailing list