On Mon, Feb 6, 2012 at 21:50, NodeJazz <infinic...@gmail.com> wrote: >> No, because the actual work - open file, read file, etc. - doesn't >> start until the next iteration of the event loop (colloquially: the >> next tick). >> > Is there a rule of thumb or API documentation that gives details about > the sync & async processing associated with a call?
The rule of thumb is that all I/O related operations are asynchronous unless explicitly marked otherwise, e.g. fs.open() vs. fs.openSync(). >> Right, I see what you mean. The system-to-node error mappings are not >> perfect yet, particularly on Windows with its myriad error codes. > > Is this just an insufficiency? I get the feeling it is some kind of > bug since the problem is seen only with a high number of connections > and it gets worse as the eventing increases. > > Would there be a way to work around the issue? Probably an insufficiency unless demonstrated otherwise. Network errors happen, even on loopback devices. -- 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 nodejs@googlegroups.com To unsubscribe from this group, send email to nodejs+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en
