Since we agree that we want to use WebClient in pharo by default, it would be nice to start pushing it into 1.2. I was waiting a bit to get some more feedback. What we could do is - load it in 1.2 - update it when andreas publish new versions - start forwarding to webClient - remove the other code slowly What do you think? Stef On Jun 10, 2010, at 4:09 PM, Sven Van Caekenberghe wrote:
Hi,
Andreas Raab's 'new' WebClient/WebServer seems quite nice, as he says himself:
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.
Is this something that will / should fit seamlessly into Pharo ? Or even become preinstalled ?
I didn't try his ConfigurationOfWebClient since the last version was unreadable and it seemed like an experiment, while his textual explanation was easy to follow.
To load it into and to make the unit tests run in Pharo 1.0 I had to make a couple of fixes (to WebCookie#printOn: and WebServer class#serverString). Who should I sent these changes to ?
But even then 1 unit test failed (#testServerDestroy).
Furthermore, some the changes in his package WebClient-Pharo seem a bit dangerous, especially a modification to SocketStream#peek (and the failed test was doing a peek) and an override of String#, some others are unneccessary as far as I can see.
Sven
-- Sven Van Caekenberghe - mailto:sven@beta9.be Beta Nine - software engineering - http://www.beta9.be .Mac - svc@mac.com - http://homepage.mac.com/svc
_______________________________________________ Pharo-users mailing list Pharo-users@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-users