Differences

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

--- at:tutorial:distribution [2009/01/29 15:38] – elisag
+++ at:tutorial:distribution [2009/01/29 15:40] – elisag
@@ Line 231: / Line 231: @@
 </note>
-More information pertaining to the API of the leased references language module can be found in the appendix.
+More information pertaining to the API of the leased references language module can be found in the [[appendix|appendix]].
 ===== Taking Offline Remote Objects =====
@@ Line 246: / Line 246: @@
 <note>
-Leased object references make use of the ''takeOffline:'' primitive to terminate the access to a remote object once the lease time elapses. Note that the ''takeOffline'' primitive can be considered the equivalent to the so-called [[http://en.wikipedia.org/wiki/Manual_memory_management|''delete'' operation]] provided by some sequential languages without built-in local garbage collection.  Rather than using this primitive for garbage collection purposes, regular AmbientTalk developers are encouraged to make use of the high-level language constructs for leasing explained in the previous section which aids them to deal with both transient and permanent disconnections and properly reclaim their remote objects.
+[[distribution#dealing_with_permanent_failures|Leased object references]] make use of the ''takeOffline:'' primitive to terminate the access to a remote object once the lease time elapses. Note that the ''takeOffline'' primitive can be considered the equivalent to the so-called [[http://en.wikipedia.org/wiki/Manual_memory_management|''delete'' operation]] provided by some sequential languages without built-in local garbage collection.  Rather than using this primitive for garbage collection purposes, regular AmbientTalk developers are encouraged to make use of the high-level language constructs for leasing explained in the previous section which aids them to deal with both transient and permanent disconnections and properly reclaim their remote objects.
 </note>