On May 15, 2014, at 9:07 AM, Frank Shearar <frank.shearar at gmail.com> wrote:

> On 15 May 2014 13:17, Tobias Pape <Das.Linux at gmx.de> wrote:
>> Hey all
>> 
>> Re-reading an old blog post
>>        https://squeakingalong.wordpress.com/2010/05/05/webclient-and-webserver-for-squeak/
>> Can we make the last paragraph happen?
> 
> (which is, for lazy folk,
> 
>> As a result, we now have what I think is a pretty decent HTTP server and client implementation for Squeak 4.1 and hopefully we can nuke HTTPSocket sometime soon. WebClient is superior in _every_ respect.
> )
> 
> frank
> 
>> Best
>>        -Tobias



I just read your blog post twice. I'm sure you're right about it being better, but if you could explain things in more detail that would be good.

1. A quick search in an image of mine says HTTPSocket is used 37 times: SMSqueakMap, SSVersion, FileStream, SocksSocket, MCHttpRepository, InstallerUrl. What happens to them? Do they all break? 
2. Would this change only work for applications that already use the *WebClient-HTTP-override protocol in HTTPSocket? 
3. Would this require the Adaptor pattern to keep older code working? 
4. If I use Kom do I need to migrate somehow? 

If you could provide more information about how this change would affect things that rely on it, then I'm all for it. 

Chris