Difference between revisions of "Actor Model"

Revision as of 00:10, 23 January 2014 (view source) Miranda ricardo (talk | contribs) ← Older edit		Revision as of 00:13, 23 January 2014 (view source) Miranda ricardo (talk | contribs) Newer edit →
Line 16:		Line 16:
	[[File:am.01.png|thumb|left|alt=Domain in decomposed in 3 subdomains creates 3 instances of MohidWater.|Domain in decomposed in 3 subdomains.]]Supose a domain in decomposed in 3 subdomains according to the image at the left. Each subdmain is an actor that sends messages to athor actors and reactes to messages it receives. Each model has a Main Loop that progresses in time-steps. Each model sends messages with border conditions to actors that need it.<br>		[[File:am.01.png|thumb|left|alt=Domain in decomposed in 3 subdomains creates 3 instances of MohidWater.|Domain in decomposed in 3 subdomains.]]Supose a domain in decomposed in 3 subdomains according to the image at the left. Each subdmain is an actor that sends messages to athor actors and reactes to messages it receives. Each model has a Main Loop that progresses in time-steps. Each model sends messages with border conditions to actors that need it.<br>
−	[[File:am.02.png|thumb|right|alt=Actor MW3 is the first actor to terminate its timestep.|(1) Actor MW3 is the first actor to terminate its timestep.]]Suppose Actor MW3 is the first actor to terminate its timestep. It sends messages to other actors with border conditions. MW3 has no messages in its mailbox so it is idle. Actor MW2 has a message in its mailbox but it can not process it yet so the message stays there.<br>	+	[[File:am.04.png|thumb|right|alt=(4) Comment.|Name.]]Every Actors are computing a timestep.<br>
−	[[File:am.03.png|thumb|left|alt=(2) Comment.|Name.]]<br>	+	[[File:am.02.png|thumb|left|alt=Actor MW3 is the first actor to terminate its timestep.|(1) Actor MW3 is the first actor to terminate its timestep.]]Suppose Actor MW3 is the first actor to terminate its timestep. It sends messages to other actors with border conditions. MW3 has no messages in its mailbox so it is idle. Actor MW2 has a message in its mailbox but it can not process it yet so the message stays there.<br>
−	[[File:am.05.png|thumb|right|alt=(3) Comment.|Name.]]<br>	+	[[File:am.03.png|thumb|right|alt=(2) Comment.|Name.]]Comment.<br>
		+
		+	[[File:am.05.png|thumb|left|alt=(3) Comment.|Name.]]Every Actors are computing a timestep again.<br>
	[[File:am.04.png|thumb|left|alt=(4) Comment.|Name.]]<br>		[[File:am.04.png|thumb|left|alt=(4) Comment.|Name.]]<br>

---

Revision as of 00:13, 23 January 2014

There are several resources in the Internet explaining the Actor Model and Reactive Programing. Some videos with interesting interviews:

• Hewitt, Meijer and Szyperski: The Actor Model (everything you wanted to know, but were afraid to ask)[1]; and
• Francesco Cesarini and Viktor Klang on the Reactive Manifesto[2].

To read online:

• The Reactive Manifesto[3]; and
• Learn You Some Erlang for great good![4];

According to the WikiPedia[5] "the actor model in computer science is a mathematical model of concurrent computation that treats "actors" as the universal primitives of concurrent digital computation: in response to a message that it receives, an actor can make local decisions, create more actors, send more messages, and determine how to respond to the next message received."

Actor Model in Mohikd

Supose a domain in decomposed in 3 subdomains according to the image at the left. Each subdmain is an actor that sends messages to athor actors and reactes to messages it receives. Each model has a Main Loop that progresses in time-steps. Each model sends messages with border conditions to actors that need it.
Every Actors are computing a timestep.
Suppose Actor MW3 is the first actor to terminate its timestep. It sends messages to other actors with border conditions. MW3 has no messages in its mailbox so it is idle. Actor MW2 has a message in its mailbox but it can not process it yet so the message stays there.
Comment.
Every Actors are computing a timestep again.