>>> 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
>