From d7dd751aa356f4f97abde84774ae9be7b11d55e4 Mon Sep 17 00:00:00 2001 From: Connor Zanin Date: Sun, 11 Dec 2016 22:43:01 -0500 Subject: . --- chapter/4/dist-langs.md | 2 -- 1 file changed, 2 deletions(-) (limited to 'chapter/4/dist-langs.md') 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 -- cgit v1.2.3