Alexey, depends on the system. Long story put short: If you have persistent workers (say one per user not per request), this can be beneficial in some situations where running user code on your machines is less costly than sending things over network or for security you cannot (ie. something akin to couchdb/mongodb/etc. indexing). This is where this approach shines.
Doing this per request... you lose some benefits from the arbiter. But the arbiter could be in any language and should exist spawning child processes if you run code anyway anyway. However, with things like SES you get pretty much full speed JS so you can get benefits from the evented nature of Node in workers while allowing some interesting interactions to take place if you are running distributed systems. Most applications see little to no gain over using a bootstrap to setup RPC and then dropping permissions from that though, which is why I mention up top that #7 is generally overkill. -- 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
