On 10/11/2011 01:59 PM, Herby VojÄÃk 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?
Pharo only supports "threaded, blocking IO", so for each WebSocket (or long-polling, or forever i-frame) connection we need to have a Process lingering around. That makes Pharo less than ideal for building a socket.io server. Cheers Philippe