Differences

This shows you the differences between two versions of the page.

--- at:tutorial:actors [2007/07/18 09:12] – Adding elisag
+++ at:tutorial:actors [2007/07/18 09:20] – elisag
@@ Line 1: / Line 1: @@
-<note>This tutorial is under heavy construction!</note>
 ====== Concurrent Programming with Actors ======
@@ Line 38: / Line 37: @@
 </note>
-The figure below summarizes AmbientTalk's concurrency model where actors are represented as communicating event loops. The dotted lines represent the event loop threads of the actors which perpetually take messages from their message queue and synchronously execute the corresponding methods on the actor's owned objects. An event loop thread never ``escapes'' its actor boundary. When communication with an object in another actor is required, a message is sent asynchronously via a far reference to the object. For example, as shown in the figure, when A sends a message to B, the message is enqueued in the message queue of B's actor which eventually processes it.
+The figure below summarizes AmbientTalk's concurrency model where actors are represented as communicating event loops. The dotted lines represent the event loop threads of the actors which perpetually take messages from their message queue and synchronously execute the corresponding methods on the actor's owned objects. An event loop thread never //escapes// its actor boundary. When communication with an object in another actor is required, a message is sent asynchronously via a far reference to the object. For example, as shown in the figure, when A sends a message to B, the message is enqueued in the message queue of B's actor which eventually processes it.
-{{:at:tutorial:concurrencymodel.png?450|:at:tutorial:concurrencymodel.png}}
+{{ :at:tutorial:concurrencymodel.png?450 |AmbientTalk actors as communicating event loops }}
 ===== Asynchronous Message Sending =====