Your English does not suck as bad as Squeak's sockets framework :) I'm in too. I can't do it all, but I can help and I can certainly set a high bar by ensuring that it works across Linux and Windows and does not lock when the network hardware loses power. Sockets are sufficiently fundamental that we should document how to use them properly AND make Pharo work that way.
________________________________________ From: pharo-project-boun...@lists.gforge.inria.fr [pharo-project-boun...@lists.gforge.inria.fr] On Behalf Of Guillermo Polito [guillermopol...@gmail.com] Sent: Monday, August 30, 2010 4:16 PM To: Pharo-project@lists.gforge.inria.fr Subject: Re: [Pharo-project] Sockets in Pharo CollaborActive Book My english sucks :P. It's "How can I help with that?" xD On Mon, Aug 30, 2010 at 5:15 PM, Guillermo Polito <guillermopol...@gmail.com<mailto:guillermopol...@gmail.com>> wrote: On Mon, Aug 30, 2010 at 5:09 PM, Stéphane Ducasse <stephane.duca...@inria.fr<mailto:stephane.duca...@inria.fr>> wrote: > Stef, Noury, > > Thanks for doing this, and for the preview! > > Sometimes being a good friend means getting tough, and it's time for that. > You are doing a great job of writing up how to create poorly designed socket > applications. They are poorly designed because of what we inherit from > Squeak. Servers should not listen for a time period; they need to listen > until told otherwise, and trigger events (notifications if preferred) when a > client tries to connect, at which point a dedicated process accepts the > connection - that process more or less is the server. Clients should try to > connect and read until told otherwise, either by a watchdog thread or by a > user. Nothing should block in either case except the calling Smalltalk > Process. If a client program does not hang because of a non-responsive > server, an interacting user has the opportunity to hit a cancel button and > put an end to wasted effort, or a watchdog can run and similarly #erminate > the offending thread. John pointed us to a kind of socket that raises events on data. Our problem is that we do not have manpower for that. > IMHO, we should not direct energy at documenting the current state of > sockets; we should do the few remaining things to get something that really > works. At the same time, we should try as much as possible to allow IrDA and > OpenSSL to appear as options. Noury and luc started to rewrite sockets using Alien and people can help. Nothing will happen magically :) How should I help with that (a little)? Cheers, Guille > > Bill _______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr<mailto: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
