On 15/09/2012, at 20:47, Mark Hahn wrote: > > ... what's a non-blocking event loop > > An imaginary mash-up of different concepts. It was a brain-fart. > > Actually, it could make sense if you think of it as an event loop that calls > non-blocking code on each tick.
But not all code is non-blocking so to compute (e.g.) fib(40) in a non-blocking manner you *need* to do it in another thread. And, that's *exactly* what node does -internally- to achieve non-blocking IO: it does it in another thread. Only that it does *not* expose any threads API to its users. Why? I don't know. But it *should*. DART provides an isolates class for that: <http://api.dartlang.org/docs/continuous/dart_isolate.html> -- Jorge. -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines You received this message because you are subscribed to the Google Groups "nodejs" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en
