aboutsummaryrefslogtreecommitdiff
path: root/chapter
diff options
context:
space:
mode:
authorConnor Zanin <cnnrznn@gmail.com>2016-12-11 22:43:01 -0500
committerConnor Zanin <cnnrznn@gmail.com>2016-12-11 22:43:01 -0500
commitd7dd751aa356f4f97abde84774ae9be7b11d55e4 (patch)
tree77af977bb0ca11334af85c096cc17312385fb54c /chapter
parent8f2e54fa75e7cc07d6593ef5ebff68e33caaabae (diff)
.
Diffstat (limited to 'chapter')
-rw-r--r--chapter/4/dist-langs.md2
1 files changed, 0 insertions, 2 deletions
diff --git a/chapter/4/dist-langs.md b/chapter/4/dist-langs.md
index f7a91a8..0059171 100644
--- a/chapter/4/dist-langs.md
+++ b/chapter/4/dist-langs.md
@@ -150,12 +150,10 @@ Because operations are serializable at the method level, the graph data-object c
Unlike DSM, communication in the actor model is explicit and exposed through message passing.
Messages can be synchronous or asynchronous, point-to-point or broadcast style.
-
In the actor model, concurrent entities do not share state as they do in DSM.
Each process, object, actor, etc., has its own address space.
The model maps well to single multicore machines as well as to clusters of machines.
Although an underlying system is required to differentiate between local and remote messages, the location of processes, objects, or actors can be transparent to the application programmer.
-
Erlang, Emerald, Argus, and Orleans are just a few of many implementations of the actor model.
#### Erlang