at:tutorial:distribution
Differences
This shows you the differences between two versions of the page.
Next revision | Previous revisionNext revisionBoth sides next revision | ||
at:tutorial:distribution [2007/04/26 19:59] – created elisag | at:tutorial:distribution [2007/04/26 20:16] – elisag | ||
---|---|---|---|
Line 1: | Line 1: | ||
+ | < | ||
+ | This tutorial is under heavy construction! | ||
+ | </ | ||
====== Distributed Programming ====== | ====== Distributed Programming ====== | ||
- | This section | + | This tutorial chapter |
- | The integration of distribution was one of the main concerns in the design of AmbientTalk programming model. More specifically, | + | The integration of distribution was one of the main concerns in the design of AmbientTalk programming model. More specifically, |
===== Starting the Network.. ===== | ===== Starting the Network.. ===== | ||
- | AmbientTalk provides an unique native object, named '' | + | AmbientTalk provides an unique native object, named '' |
+ | |||
+ | When the virtual machine | ||
< | < | ||
Line 47: | Line 52: | ||
</ | </ | ||
- | The code block to execute when the service type becomes available is parameterized with the actual remote reference to the discovered service object. In the example above, '' | + | The code block to execute when the service type becomes available is parameterized with the actual remote reference to the discovered service object. In the example above, '' |
+ | < | ||
+ | We are using a future to get the return value of the '' | ||
+ | </ | ||
- | The observer installed with the '' | + | The '' |
+ | |||
+ | As '' | ||
+ | |||
===== Partial Failure Handling ===== | ===== Partial Failure Handling ===== | ||
- | Let us consider again the example instant messenger application described in previous | + | Let us consider again the example instant messenger application described in previous |
+ | |||
+ | When an object discovers a service type, the '' | ||
- Objects are always passed by far reference, except for isolate objects which are passed by copy. | - Objects are always passed by far reference, except for isolate objects which are passed by copy. | ||
- Native data types are always passed by copy. | - Native data types are always passed by copy. | ||
+ | |||
When a remote far reference receives a messages, it flushes the message to the remote object providing that it is connected. If the remote far reference is disconnected, | When a remote far reference receives a messages, it flushes the message to the remote object providing that it is connected. If the remote far reference is disconnected, |
at/tutorial/distribution.txt · Last modified: 2009/01/30 16:13 by tvcutsem