<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On Sep 29, 2010, at 11:31 AM, <a href="mailto:exarkun@twistedmatrix.com">exarkun@twistedmatrix.com</a> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><span class="Apple-style-span" style="border-collapse: separate; font-family: Menlo; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; font-size: medium; "><span class="Apple-style-span" style="font-family: monospace; ">First there would be tickets (plural) for adding features to Twisted's<span class="Apple-converted-space"> </span><br>Request and FakeRequest from Nevow. Then there would be tickets (or<span class="Apple-converted-space"> </span><br>maybe just a ticket) for deleting the corresponding (then redundant)<span class="Apple-converted-space"> </span><br>code from Nevow.<br></span></span></blockquote></div><br><div>My two cents here would be to move in the direction of making Request itself a data structure which could be manipulated in memory, rather than having it tightly bound to the HTTP connection, and then having a discrete test double.</div></body></html>