<div class="gmail_quote">On Sun, Oct 28, 2012 at 9:17 PM, Glyph <span dir="ltr"><<a href="mailto:glyph@twistedmatrix.com" target="_blank">glyph@twistedmatrix.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div style="word-wrap:break-word">Since there's no supported way to transplant a transport (see <<a href="http://tm.tl/3204" target="_blank">http://tm.tl/3204</a>>)... yes.<div></div></div></blockquote><div><br>
Aha!<br> </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>But, even if you were going to rely on undefined behavior and private APIs, I don't see anything in your code sample that changes anything on the <i>transport</i> to point at your new protocol. So I don't see why you would think that it would start calling methods on it :).</div>
</div></blockquote><div><br>For some reason I thought IProtocol.makeConnection did that; I guess it's because the implementation in Protocol sets the `transport` attribute (I thought it was the other way around).<br>
<br>
I've set transport.protocol = myNewProtocol and now there's one extra passing acceptance test.<br><br>I'm slowly beginning to wonder if it wouldn't be easier to write it from scratch using t.w.websockets from the get-go...<br>
</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"><span class="HOEnZb"><font color="#888888"><div>-g</div><div><br></div></font></span></div>
<br>_______________________________________________<br>
Twisted-Python mailing list<br>
<a href="mailto:Twisted-Python@twistedmatrix.com">Twisted-Python@twistedmatrix.com</a><br>
<a href="http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python" target="_blank">http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python</a><br>
<br></blockquote></div><br><br clear="all"><br>-- <br>cheers<div>lvh</div><br>