Are you intent on replacing <meta http-equiv="content-type" content="text/html; charset=utf-8"><span class="Apple-style-span" style="font-family: arial, sans-serif; font-size: 13px; border-collapse: collapse; ">HTTPSocket in the long run? I have an RPC-ish thing that uses it, so I'd like to be clear on whether I can expect it to be around for the next release.</span><br>
<br><div class="gmail_quote">On Tue, May 4, 2010 at 10:14 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;">
Folks -<br>
<br>
I'm happy to announce the release of WebClient and WebServer 1.0 for Squeak 4.1. I started this little side project about half a year ago when I realized that I had just written the third almost-but-not-quite complete HTTP server implementation internally. The thing is, HTTP servers and clients are tremendously useful. Having a small and compact implementation offers all sorts of interesting uses. For example, we use HTTP as command and control interface for various backend server aspects; be that generating status XML for processing by a front-end php app, or profiling of the live application, or RTSP handling, or server-to-server communication. Given all these interesting simple applications I figured it was about time to write a *simple* general purpose HTTP server (yes, I'm looking at you Kom).<br>
<br>
While writing it I quickly noticed that I need an accompanying client since HTTPSocket was just too awful for testing. It's incomplete, inconsistent and broken in lots of interesting ways. The good thing is that since both client and server share much of the representation, the overhead is very small.<br>
<br>
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>
<br>
Oh, one word about the name: HTTPxxx is taken, HttpXxxx is taken, so I was left with the choice of either going for HtTpClient / HtTpServer, or WebClient / WebServer. The name's a little broad, granted, but better than mixed caps :-)<br>
<br>
>From the project page (<a href="http://www.squeaksource.com/WebClient" target="_blank">http://www.squeaksource.com/WebClient</a>):<br>
<br>
-------------------------------------------------------------------<br>
<br>
Project Description<br>
WebClient and WebServer are simple, compact, and easy to use HTTP client and server implementations.<br>
<br>
Installation<br>
To install WebClient and WebServer, execute the following from a Workspace in Squeak:<br>
<br>
(Installer ss project: 'WebClient')<br>
install: 'WebClient-Core';<br>
install: 'WebClient-Tests';<br>
install: 'WebClient-Help'.<br>
<br>
In addition to the core functionality, a set of patches is provided by the 'WebClient-HTTP' package replacing HTTPSocket by WebClient (which means WebClient will be used for Monticello, updates etc):<br>
<br>
(Installer ss project: 'WebClient')<br>
install: 'WebClient-HTTP';<br>
<br>
An experimental Seaside 3.0 adapter for WebServer is available in the 'WebClient-Seaside' package:<br>
<br>
(Installer ss project: 'WebClient')<br>
install: 'WebClient-Seaside';<br>
<br>
Help is provided via HelpSystem but make sure you also look at the example in class WebClient and WebServer itself.<br>
<br>
-------------------------------------------------------------------<br>
<br>
Cheers,<br><font color="#888888">
- Andreas<br>
<br>
</font></blockquote></div><br><br clear="all"><br>-- <br>Casey Ransberger<br>