<html><head><meta http-equiv="Content-Type" content="text/html charset=iso-8859-1"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On Oct 28, 2012, at 8:17 AM, Laurens Van Houtven <_@lvh.cc> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><span style="font-family: Menlo; font-size: medium; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; display: inline !important; float: none; ">This leads me to believe I'm essentially just screwing up transplanting this transport entirely. Is that the case?</span><br clear="all" style="font-family: Menlo; font-size: medium; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; "></blockquote></div><br><div>Since there's no supported way to transplant a transport (see <<a href="http://tm.tl/3204">http://tm.tl/3204</a>>)... yes.</div><div><br></div><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><br></div><div>-g</div><div><br></div></body></html>