Requests mechanism of Node.JS and IIS (event-loop and threading) -


i'm trying figure out advantage of node.js event-loop mechanism (publish , subscribe c++ threadpool) on way iis handling requests.

i've read here: http://rickgaribay.net/archive/2012/01/28/node-is-not-single-threaded.aspx , line: "there no context switching event loop publishes , subscribes thread pool." not clear me.

iis has i/o thread send request clr thread pool, , continues work until receives response. kind of similar event loop i've understood. cpu switching between threads, switches worker threads of node (in order work done) , same-same clr thread pool.

can please explain key advantage of event-loop mechanism on request threading iis uses ?

i think author link adds more confusion clarity (the guy says learning node, you're asking blind-leading-the-blind situation in using learn from). don't know why thinks node claims "it" (i.e. node.js) single threaded. have never seen that. point within node your code executes in single thread means developer freed dealing contention of different sorts. (many people see key advantage, think 1 argue trading 1 kind of boilerplate (for semaphores or like) another: handling of asynchrony (although several approaches exist reducing more tedious aspects of this).

although i'm not asking, think if watch video (https://www.youtube.com/watch?v=l0pjvcisu6a) between 3 minute , 7 minute marks, have "oh, it" moment. visual representation presenter uses (which believe takes in part preso original node creator) far easier understand wall of text describe same thing using words alone.

hope helps.


Comments

Popular posts from this blog

blackberry 10 - how to add multiple markers on the google map just by url? -

php - guestbook returning database data to flash -

delphi - Dynamic file type icon -