But, what should you do if you can't serve anything after all sub-processes have completed their work?
Am Donnerstag, 14. März 2013 22:02:11 UTC+1 schrieb Mikeal Rogers: > > That's a great "oppertunity?" but it's not in line with the structure and > goals of node.js. > > Node has synchronous file operations. The reason it has sync file > operations is that there are many cases where you actually **want** to stop > the entire server until you get back data from the filesystem because you > can't server **any** requests until it's come back. In this case, not only > is a sync file operation required, it's actually more efficient than using > an async operation (at least in node.js). > -- -- 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 --- 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 nodejs+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
