Funny comment inline below...<br><br><div class="gmail_quote">On Tue, May 4, 2010 at 11:22 PM, Andreas Raab <span dir="ltr"><<a href="mailto:andreas.raab@gmx.de">andreas.raab@gmx.de</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="im">On 5/4/2010 11:11 PM, Casey Ransberger wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Are you intent on replacing HTTPSocket in the long run? I have an<br>
RPC-ish thing that uses it, so I'd like to be clear on whether I can<br>
expect it to be around for the next release.<br>
</blockquote>
<br></div>
In the long run: Yes. In the next release: No. And "replacing" can mean that the public interface in HTTPSocket remains. That's what the WebClient-HTTP package does. It patches HTTPSocket to use WebClient while preserving the identical external interface.<br>
</blockquote><div><br></div><div>I'm beginning to recognize a pattern in your behavior:)</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><snip><br>
Cheers,<br><font color="#888888">
- Andreas<br><font class="Apple-style-span" color="#000000"><font class="Apple-style-span" color="#888888"><br></font></font></font></blockquote></div>-- <br>Casey Ransberger<br>