<html><head><meta http-equiv="Content-Type" content="text/html charset=windows-1252"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><br><div><div>On May 15, 2014, at 1:21 PM, Tobias Pape <<a href="mailto:Das.Linux@gmx.de">Das.Linux@gmx.de</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div style="font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;">Hey,<br><br>On 15.05.2014, at 17:41, Chris Cunnington <<a href="mailto:brasspen@gmail.com">brasspen@gmail.com</a>> wrote:<br><br><blockquote type="cite"><br>On May 15, 2014, at 9:07 AM, Frank Shearar <<a href="mailto:frank.shearar@gmail.com">frank.shearar@gmail.com</a>> wrote:<br><br><blockquote type="cite">On 15 May 2014 13:17, Tobias Pape <<a href="mailto:Das.Linux@gmx.de">Das.Linux@gmx.de</a>> wrote:<br><blockquote type="cite">Hey all<br><br>Re-reading an old blog post<br> <a href="https://squeakingalong.wordpress.com/2010/05/05/webclient-and-webserver-for-squeak/">https://squeakingalong.wordpress.com/2010/05/05/webclient-and-webserver-for-squeak/</a><br>Can we make the last paragraph happen?<br></blockquote><br>(which is, for lazy folk,<br><br><blockquote type="cite">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.<br></blockquote>)<br><br>frank<br><br><blockquote type="cite">Best<br> -Tobias<br></blockquote></blockquote><br><br><br>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.<br><br></blockquote><br>Attention, the post is not mine. It is an old one by Andreas.<br></div></blockquote><div><br></div>Ah, my mistake. <br><blockquote type="cite"><div style="font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;"><br><blockquote type="cite">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?<span class="Apple-converted-space"> </span><br></blockquote><br>Well, Andreas introduced that Compat layer<span class="Apple-converted-space"> </span><br>as you found out (Q2).<br>So they theoretically shouldn't.<br></div></blockquote><div>Great. </div><blockquote type="cite"><div style="font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;"><br>(BTW, If SSVersion is from SqueakSource, how would it use HTTPSocket?)<br></div></blockquote>SSVersion>>#registerSqueakMap: </div><div>I imagine it was removed a long time ago from the SqueakSource code base. It looks like it was an idea that was not fully realized. I have no intention in using it for SMServer. <br><blockquote type="cite"><div style="font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;"><br><blockquote type="cite">2. Would this change only work for applications that already use the *WebClient-HTTP-override protocol in HTTPSocket?<span class="Apple-converted-space"> </span><br></blockquote><br>There shouldn't be any other uses…<br><br><blockquote type="cite">3. Would this require the Adaptor pattern to keep older code working?<span class="Apple-converted-space"> </span><br></blockquote><br>An inverse for WebClient-HTTP so to speak…<br><br><blockquote type="cite">4. If I use Kom do I need to migrate somehow?<span class="Apple-converted-space"> </span><br></blockquote><br>I don't know.</div></blockquote><blockquote type="cite"><div style="font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;"><blockquote type="cite"><br>If you could provide more information about how this change would affect things that rely on it, then I'm all for it.<span class="Apple-converted-space"> </span><br></blockquote><br>• We should be just concerned to migrate the core infrastructure<br> (Monticello, Updates, SqueakMap if you want, Installer if necessary)<br>• Move HTTPSocket into its own package<br>• Deprecate HTTPSocket in 4.6 or 4.7<br>• Remove it in 4.7 or 4.8<br><br>I just jumped for it as I hat to answer questions regarding problems in HTTPSocket<br>and I just noticed that it is really due to be replaced, IMHO.<br></div></blockquote><br><div>Sounds like a great idea. </div><br><blockquote type="cite"><div style="font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;"><br>Best<br><span class="Apple-tab-span" style="white-space: pre;"> </span>-Tobias</div></blockquote></div><br></body></html>