On 11 October 2011 13:59, Herby Vojčík <[email protected]> wrote: > > Philippe Marschall-2 wrote: >> >> On 10/10/2011 09:47 PM, Herby Vojčík wrote: >>> Is there / planning a socket.io (server) support in Pharo? I am making >>> suite >>> of client-server application where I strongly consider socket.io as the >>> communication layer; there is no problem with clients, but at the >>> server-side, socket.io seems only to be supported by its native node.js >> >> Without async IO supporting WebSockets does not seem to make much sense. >> >> ... >> >> Cheers >> Philippe >> > > I do not understand the rationale... "async IO" (more correctly, as Ryan > Dahl often points, is "non-blocking IO", there is nothing async in node.js, > it's single-threaded) is just the alternative model to "threaded, blocking > IO". What does it have in common with sense of making WebSockets work? > > Nevertheless, it seems there is no support of server-side socket.io in > Pharo, I conclude. :-( >
Sockets in Pharo are not blocking the whole VM. What they block is the process which working with concrete socket. But other processes can still run, while one waiting data / even from single socket. > Thanx, Herby > > -- > View this message in context: > http://forum.world.st/socket-io-tp3891592p3893938.html > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. > > -- Best regards, Igor Stasenko.
