Hey Norman, To address some of your comments I'd like to point out some assumptions that may or may not be true.
For example, an assumption that Kernel is separate from an actor system. One of the things I've been looking at recently is to write a "kernel" in actors. But, there already exist projects which bypass the Kernel, for example the Erling (aka Erlang on Xen) has no Kernel as we "usually" think of it and boots straight into the Erlang VM (http://erlangonxen.org/). Then again, one can think of an Erlang VM as the kernel, so it's difficult to pin it down. The Supervisor thing is really a pattern of how to set up systems made from actors. It has been demonstrated by Erlang to be a useful pattern, as you pointed out, for fault/error detection, but is not in itself a necessity to run an actor system (although, it is very useful). As to Actors having to respond, that's also an assumption. An actor does not need to respond to any message using a request-reply pattern. Passing a message through a supervisor would not be a problem in well constructed actor systems because you'd always include a "customer" as part of the message. In Node.js you'd think of it as a callback that keeps getting passed around between calls until finally invoked. It's a continuation pattern. Cheers, Tristan On Wednesday, September 25, 2013 8:39:48 AM UTC-5, Norman Paniagua wrote: > > So many new concepts here to me, and thats teach me that I'm just know > almost nothing. > > I would like to develop a library, only for learning purpose, I'll read > those links that Tristan shares. > > Angel seems very interesting your project, its also for learning purpose > yet? > > There is so many things that I really don't understand, one of them is how > really Actors work, as far I understand basically an app have 3 elements: > > - Kernel: it start the system and supervise the root actors. > - Supervisor: is an actor that supervise other actors. > - Actor: its just an actor. > > Then each actor has their own route (to receive messages), but if you can > talk to each actor without pass through their supervisor, what is their > purpose (of the supervisor)? just know it the actor dies to restart it? or > the message must pass through their supervisor before reach the destination > actor? How the actor respond and to who (maybe I think much as web > developer, that everything has an response and must reach the user)? > > Regards > > -- > Norman Paniagua > -- -- 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.
