Phillip J. Eby wrote: > Hi. I've heard recently that there are some tests that ideally would > need to run under the Twisted reactor, in order to properly exercise the
/me raises his hand. > from the underlying transport mechanism in use. About the only > "interesting" part would likely be SSL/TLS, since I doubt M2Crypto and > OpenSSL will want to talk to mocket objects instead of real sockets. It > might be necessary to create mock SSL "Transport" objects as well as a > mock reactor. Yeah, OpenSSL is a problem, at least if you want to test it fully. However, since we are primarily interested in the TwistedProtocolWrapper.TLSProtocolWrapper object, things should be much easier. That class gets cleartext passed in from Twisted, which the class then encrypts using in-memory BIOs (OpenSSL's input/output abstraction layer), then passes the encrypted data back to Twisted. And vice versa when Twisted feeds encrypted data to the class, of course. So, if the mock reactor can feed this class data through mockets, things should just work. -- Heikki Toivonen
signature.asc
Description: OpenPGP digital signature
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ Open Source Applications Foundation "Dev" mailing list http://lists.osafoundation.org/mailman/listinfo/dev
