User Tools

Site Tools


at:tutorial:distribution

Differences

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

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
Next revisionBoth sides next revision
at:tutorial:distribution [2007/04/26 20:13] elisagat:tutorial:distribution [2007/04/26 20:16] elisag
Line 1: Line 1:
 +<note>
 +This tutorial is under heavy construction!
 +</note>
  
 ====== Distributed Programming ====== ====== Distributed Programming ======
  
-This section discusses how AmbientTalk virtual machines can discover and communicate with each other over the network.  +This tutorial chapter discusses how AmbientTalk virtual machines can discover and communicate with each other over the network.  
-The integration of distribution was one of the main concerns in the design of AmbientTalk programming model. More specifically, as a distributed programming languages that adheres to the Ambient-Oriented Programming paradigm, AmbientTalk incorporates partial failures and discovery lookup facilities at the heart of its distributed programming model. Rather than creating stubs and skeletons to manage remote communications, AmbientTalk integrates them transparently to the developer thanks to its concurrency model based on actors and far references. Far references are in fact a vital feature of the distributed model of AmbientTalk that allows the language to be able to handle the so-called volatile connections featured in mobile ad hoc networks.  This section mainly explains the language abstractions to export and discover other remote objects, and handle partial failures. But first, let us start simply by showing how to enable the network functionality.+The integration of distribution was one of the main concerns in the design of AmbientTalk programming model. More specifically, as a distributed programming languages that adheres to the Ambient-Oriented Programming paradigm, AmbientTalk incorporates partial failures and discovery lookup facilities at the heart of its distributed programming model. Rather than creating stubs and skeletons to manage remote communications, AmbientTalk integrates them transparently to the developer thanks to its concurrency model based on actors and far references. Far references are in fact a vital feature of the distributed model of AmbientTalk that allows the language to be able to handle the so-called volatile connections featured in mobile ad hoc networks.  This chapter mainly explains the language abstractions to export and discover other remote objects, and handle partial failures. But first, let us start simply by showing how to enable the network functionality.
  
 ===== Starting the Network.. ===== ===== Starting the Network.. =====
Line 61: Line 64:
 ===== Partial Failure Handling ===== ===== Partial Failure Handling =====
  
-Let us consider again the example instant messenger application described in previous subsection to further explain the semantics of AmbientTalk's remote object references and how they deal with transient disconnections. +Let us consider again the example instant messenger application described in previous section to further explain the semantics of AmbientTalk's remote object references and how they deal with transient disconnections. 
  
 When an object discovers a service type, the ''when'' observers are triggered receiving as parameter a remote far reference to the remote object discovered. As explained in previous sections, far references operates asynchronously. When a client object sends a message via a remote reference, the message is buffered in the remote far reference and the client does not even wait for the message to be delivered. This is crucial in distributed computing in order to prevent race conditions. The parameter passing in the context of distribution works similar to the inter-actor message sending semantics: When an object discovers a service type, the ''when'' observers are triggered receiving as parameter a remote far reference to the remote object discovered. As explained in previous sections, far references operates asynchronously. When a client object sends a message via a remote reference, the message is buffered in the remote far reference and the client does not even wait for the message to be delivered. This is crucial in distributed computing in order to prevent race conditions. The parameter passing in the context of distribution works similar to the inter-actor message sending semantics:
at/tutorial/distribution.txt · Last modified: 2009/01/30 16:13 by tvcutsem