Differences

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

--- at:tutorial:distribution [2008/06/25 17:31] – added tvcutsem
+++ at:tutorial:distribution [2008/09/16 17:29] – * tvcutsem
@@ Line 7: / Line 7: @@
 Before delving in these topics, we illustrate how to activate the network facilities of AmbientTalk in the next section.
-===== Starting the Network.. =====
+===== Going Online =====
 AmbientTalk provides an unique native object, named ''network'',  that responds to two methods that control the network access to an AmbientTalk virtual machine. More specifically, ''network.online()'' and ''network.offline()'' make a virtual machine go online and offline, respectively.
@@ Line 107: / Line 107: @@
 ===== Garbage collecting remote references =====
+<note>
+This is an advanced topic and probably does not belong in the tutorial. Moreover, it discusses features to be used only by implementors of reflective language constructs. It would better be replaced by a thorough explanation of leased object references.
+</note>
 As explained in the previous section, AmbientTalk's remote references are by default resilient to disconnections. This has significant repercussions at a distributed memory management level. The main impact is that an exported object cannot be reclaimed when all of its clients are disconnected since the remote references remain pointing to the server object. In other words, servers objects are kept alive even though there are only remotely accessible by a disconnected remote reference. AmbientTalk provides built-in support to unexport explicitly remotely accessible objects by means of the ''takeOffline'' language construct. The construct look as follows: