On Saturday, April 11, 2015 at 10:46:12 PM UTC-4, Ingwie Phoenix wrote:
> When we now use cluster.isMaster and cluster.isChild… what behaviour could > be expected from the above structure? I saw C programs doing a fork-in-fork > mechanism, but not in NodeJS, especially since in this case, a script is > ran again from top to bottom - and not just copied into new memory and > executed at the same point, like it happens in POSIX fork() and php-pcntl > pcntl_fork(). > Sounds like those should be separate processes anyway. they don't share much or anything, not that fork is easy to get right in such a managed runtime. One process doing one thing -- should serve you well. -- 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/db519bdd-1361-401b-a978-f2784f557330%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
