A simple example, You are starting reading a file a really huge file upon arrival of the request. Any other event handler will be triggered even though file reading is not complete.
Thanks, On Monday, August 17, 2015 at 9:08:12 PM UTC-7, Xiao wrote: > > Hi All, > > I am new to Node.js. What is the exact meaning of non-blocking I/O > operation in Node.js. Is that only for the whole process of one client > request, or it is used in the thread of Node.js. The difference here is > mean, if it is for one client request, the Node.js will be blocked until > the current request is finished, and then handle the next one. If it is for > the Node.js thread, the Node.js will push the response callback into the > event loop, and then handle the next request. I think the second one should > be the correct one, because it is using V8 as the engine, but for my > application, it acts the first way. Which is the correct behavior for > Node.js or do I need some configuration changes for that? > > Thanks. > -- Job board: http://jobs.nodejs.org/ New group rules: https://gist.github.com/othiym23/9886289#file-moderation-policy-md Old group rules: 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 unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/nodejs/5d6d1b90-f145-463e-81b7-56cb0a1af409%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
