<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On Oct 26, 2012, at 7:16 AM, Itamar Turner-Trauring <<a href="mailto:itamar@futurefoundries.com">itamar@futurefoundries.com</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><br><br><div class="gmail_quote">On Thu, Oct 25, 2012 at 6:32 PM, Glyph <span dir="ltr"><<a href="mailto:glyph@twistedmatrix.com" target="_blank">glyph@twistedmatrix.com</a>></span> wrote:<br><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div style="word-wrap:break-word"><div>There are three (count them, three!) classes called "IOPump" in various Twisted test-support modules. Please note that <b>unlike the stuff in proto_helpers these are not supported and will likely go away in a future version of Twisted</b>. However, they do provide a simple demonstration of how to hook up a client and server (calling dataReceived() with what transport.write() produced).</div>
<div><br></div><div>If you'd like to help Twisted itself, we could really use a patch that cleans up all three of those implementations of IOPump, tests them, documents them, and exposes them in a way that would be beneficial to those writing tests like yours.</div>
</div></blockquote><div><br>I guess none of the loopback implementations in twisted.protocols.loopback use StringTransport? <br></div></div></blockquote><br></div><div>Nope, it has <i>two</i> other transport implementations - _LoopbackTransport and LoopbackRelay; plus, unlike what IOPump does, loopback is written to encourage you to return a Deferred from your test, which is generally a bad idea if you can easily avoid it.</div><div><br></div><div>-glyph</div><br></body></html>