The deeper question is whether we want to document how things are, or they they *should be* - which is VERY much different from the eventless and timeout ridden design that we have now. It desperately needs to be redesigned.
________________________________________ From: pharo-project-boun...@lists.gforge.inria.fr [pharo-project-boun...@lists.gforge.inria.fr] On Behalf Of Sean P. DeNigris [s...@clipperadams.com] Sent: Tuesday, August 31, 2010 10:41 PM To: pharo-project@lists.gforge.inria.fr Subject: Re: [Pharo-project] Sockets in Pharo CollaborActive Book Michael Roberts-2 wrote: > > The example > <snip> > is only server side. If you follow the sections, you can see I used > netcat as the client and illustrated some simple cmd line debugging > techniques. the code above whilst it could of course contains bugs > and not use the right API is consistent in what it tries to do. > Ah, okay. Now I got it. The client temporary variable, along with the fact that this snippet is a section to itself confused me and I didn't keep reading. >so is this where we want to direct people first? Michael Roberts-2 wrote: > > well, no, but sockets are fundamental and should be explained. I had > only imagined it the seed for something bigger. the colab book will > not expand unless people start somewhere. It is a work in progress as > well, remember that... > Cool, I appreciate you getting the ball rolling - I am trying to push it further! (and I don't know too much about sockets) Sean -- View this message in context: http://forum.world.st/Sockets-in-Pharo-CollaborActive-Book-tp2399361p2402542.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com. _______________________________________________ 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
