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/04/24 21:04] – * 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 striped | + | < |
+ | If the object referred to by a far reference is tagged | ||
+ | </ | ||
+ | |||
+ | The figure below summarizes AmbientTalk' | ||
+ | |||
+ | {{ : | ||
===== Asynchronous Message Sending ===== | ===== Asynchronous Message Sending ===== | ||
Line 107: | Line 112: | ||
}; | }; | ||
}; | }; | ||
- | >>< | + | >>< |
</ | </ | ||
- | The '' | + | The '' |
An isolate differs from a regular object as follows: | An isolate differs from a regular object as follows: | ||
Line 132: | Line 137: | ||
</ | </ | ||
- | < | + | < |
A word of warning: isolates are objects that are copied freely between actors. As a result, they should be objects whose actual object identity is of little importance. Usually, the identity of by-copy objects is determined by the value of some of the object' | A word of warning: isolates are objects that are copied freely between actors. As a result, they should be objects whose actual object identity is of little importance. Usually, the identity of by-copy objects is determined by the value of some of the object' | ||
< | < | ||
Line 245: | Line 250: | ||
</ | </ | ||
- | Or, you can specify a stripe | + | Or, you can specify a type tag to only catch specific exceptions: |
< | < | ||
Line 276: | Line 281: | ||
When the future for ''< | When the future for ''< | ||
- | ==== Futures and Striped | + | ==== Futures and Annotated |
- | As previously explained, there are two modes for enabling futures in AmbientTalk. Invoking '' | + | As previously explained, there are two modes for enabling futures in AmbientTalk. Invoking '' |
- | When a message send is striped | + | When a message send is annotated |
< | < | ||
Line 286: | Line 291: | ||
</ | </ | ||
- | When a message send is striped | + | When a message send is annotated |
< | < |
at/tutorial/actors.txt · Last modified: 2020/02/05 21:26 by elisag