I agree and this is why I asked. I'm not good in network but the code of network always made me nearly faint because it was clearly not designed. Now why interested people would not do a little task forces to bullet proof the integration and we prepare together its integration... remember pharo is also your smalltalk :)
On Jul 6, 2010, at 3:04 PM, Sven Van Caekenberghe wrote: > Yes!! > > It now loads without patches into Pharo 1.1 rc2 > I used its client and server part, seaside adaptor, it all works. > > The code is quite readable/understandable/malleable. > > I did not yet test the WebClient-HTTP package which patches HTTPSocket to > replace the old code, > which is obviously important (it then gets used by MC and the rest of > Smalltalk). > > The unit tests also have to be double checked. > > What do others, like Lukas and other Seaside people think of it ? > > The basic point it: it can only be better than the older code. > But on the other hand, maybe the leap could be even bigger still ? > Having a facade for a pluggable http client is one step. > > Having a good basic HTTP client and server is very important. > > Sven > > On 06 Jul 2010, at 09:30, Stéphane Ducasse wrote: > >> to replace the old code? >> >> Stef >> >> _______________________________________________ >> Pharo-project mailing list >> [email protected] >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > _______________________________________________ > Pharo-project mailing list > [email protected] > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project _______________________________________________ Pharo-project mailing list [email protected] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
