at:tutorial:actors
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
at:tutorial:actors [2007/06/19 16:14] – * tvcutsem | at:tutorial:actors [2007/07/18 09:20] – elisag | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | < | ||
====== Concurrent Programming with Actors ====== | ====== Concurrent Programming with Actors ====== | ||
Line 32: | Line 31: | ||
As you can see, actors are created similar to objects. The '' | As you can see, actors are created similar to objects. The '' | ||
- | So what exactly is a far reference to an object? The terminology stems from the E language: it is an object reference that refers to an object hosted by another actor. The main difference between regular object references and far references is that regular references allow direct, synchronous access to an object, while far references | + | So what exactly is a far reference to an object? The terminology stems from the E language: it is an object reference that refers to an object hosted by another actor. The main difference between regular object references and far references is that regular references allow direct, synchronous access to an object, while far references |
- | Note that, if the object referred to by a far reference is tagged with one or more type tags, the far reference itself is tagged with the same type tags. Hence, an object located on a remote actor can be tested for its types // | + | < |
+ | If the object referred to by a far reference is tagged with one or more type tags, the far reference itself is tagged with the same type tags. Hence, an object located on a remote actor can be tested for its types // | ||
+ | </ | ||
+ | |||
+ | The figure below summarizes AmbientTalk' | ||
+ | |||
+ | {{ : | ||
===== Asynchronous Message Sending ===== | ===== Asynchronous Message Sending ===== |
at/tutorial/actors.txt · Last modified: 2020/02/05 21:26 by elisag