On Sep 1, 2010, at 8:58 AM, Göran Krampe wrote: > Hi all! > > Two notes (no, haven't read all posts on this subject): > > 1. IMHO for almost 99% of your needs you would use SocketStream and not > Socket directly to write a socket client. I wrote the current SocketStream > implementation and I have written several clients using it - like the latest > StompProtocol on SS etc. Please, please, use SocketStream in your > introduction to socket client programming!
Yes this is the missing section in noury/luc chapter :) > 2. I haven't looked at Andreas' new WebServer but I presume it is a > "standard" forking server just like the old Comanche/KomHttpServer codebase > is. A while back I wrote Blackfoot - a SimpleCGI implementation and then I > extracted the essential "forking Socket server" code from KomHttpServer so > that it can be easily understood and reused. I tend to point to Blackfoot as > a very good "example" to use in this regard. We could even split out the > generic part as a "standard class" to use. In fact, Stephen Pair did this > with the TcpServices library a long time ago when he rewrote Comanche into > KomHttpServer BUT... I think it got a bit overengineered and would instead > point to Blackfoot as a good candidate for such a "SocketServer" class. sound cool do you have a little 2 pages intro to blackfoot? Stef > > > regards, Göran > > _______________________________________________ > Pharo-project mailing list > Pharo-project@lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project _______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
