Yes,<div>ok for me to replace *Socket with WebClient.</div><div>Thanks</div><div>Bye</div><div>Enrico<br><br><div class="gmail_quote">On Thu, Jun 17, 2010 at 05:07, 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;">Hi -<br>
<br>
I'm interested in doing a little assault on the aforementioned classes. The only reason for the existence of Old[SimpleClient]Socket is that they're superclasses of HTTPSocket which is a beast to get rid of since we need it for updating etc.<br>
<br>
However, with WebClient [1] at hand, we can convert HTTPSocket into a simple facade that just delegates everything to WebClient and in addition to having a better HTTP client implementation we could also get rid of these Old* classes.<br>
<br>
What do people think? Is there any value in preserving the Old* classes and HTTPSocket or should we try to take an end-run on the issue? Obviously, there will be some tricky updating involved so I'd like to get opinions beforehand.<br>
<br>
Cheers,<br>
- Andreas<br>
<br>
[1] <a href="http://www.squeaksource.com/WebClient.html" target="_blank">http://www.squeaksource.com/WebClient.html</a><br>
<br>
</blockquote></div><br><br clear="all"><br>-- <br>Enrico Spinielli<br>"Do Androids dream of electric sheep?"— Philip K. Dick<br>"Hear and forget; see and remember;do and understand."—Mitchel Resnick<br>
</div>