Hey.
Imagine you have the following structure:
main
* http worker#1
* http worker#2
* api worker#1
This is a structure that can easily be done with the cluster module. But what
if we have one major watchdog process and the structure changes to this?
watchdog
- http server
* worker#1
* worker#2
- api server
* worker#1
This would require the watchdog process to fork() into two separate processes
that it can savely watch. Then, these subprocesses would have to fork() N times
for their workers.
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().
Kind regards, Ingwie
--
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/6DB78DEB-A339-4485-90F3-267D4BDB74F6%40googlemail.com.
For more options, visit https://groups.google.com/d/optout.
