> I remember a project called Tripwire (https://npmjs.org/package/tripwire) > that attempts to kill blocking code. >
That's pretty cool. Thanks. > With the design I'm proposing, creating an actor will spawn a new thread > with its own event loop waiting to receive messages. I'm not sure on the > cost of that, but it would be interesting to find out. > What about a go-routine-like model (instead of thread spawning)? Sure, but those addresses don't work when you scale beyond a single > process. I'm not sure how to solve that problem yet. > Yes, Mark's references seem a step in the right direction. Ken uses unguessable web-keys (referenced in the paper he mentioned: http://eros-os.org/pipermail/cap-talk/2012-September/015386.html). > -- -- 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 [email protected] To unsubscribe from this group, send email to [email protected] 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 [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
