For Ocean to succeed, you either have to work really hard to make non-blocking calls (I'm thinking of SSL sockets), or you need the ability to call functions on OS threads. The calls need to block their calling Process and let the other Processes run as though nothing is happening. ________________________________________ From: pharo-project-bounces@lists.gforge.inria.fr [pharo-project-bounces@lists.gforge.inria.fr] On Behalf Of Noury Bouraqadi [bouraqadi@gmail.com] Sent: Sunday, October 03, 2010 4:57 AM To: Pharo-project@lists.gforge.inria.fr Subject: [Pharo-project] Less plugins, more Smalltalk code! (was: Re: Pharo 1.1.1 OneClickCogVm) On 30 sept. 2010, at 20:22, Germán Arduino wrote:
2010/9/30 Sven Van Caekenberghe <sven@beta9.be>:
Less plugins, more Smalltalk code! I want to look at everything and never see C. Plugins/primitives should only be there when they are absolutely necessary (to access a platform feature or for crucial performance).
Sven
+1
Yes. This is the approach we advocate in the Ocean project. We would like to see it generalized beyond the network library. Noury _______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project