Differences

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

--- research:dgc [2006/07/01 15:30] – elisag
+++ research:dgc [2006/07/01 15:32] – elisag
@@ Line 9: / Line 9: @@
 ==== Design ====
-Semi-automatic garbage collection is a hybrid approach which relies on an underlying local GC and proposes a non-transparent DGC. The approach can be seen as an extension to the indirect reference counting (Piquer,1991) and network objects (Birrell et al.m 1993) since it also maintains the distributed inverse reference graph (IRG) where each remote object keeps a list of pointers to other devices which have references to it. However, the IRG is augmented with additional semantic information attached to the remote references to help the collector to determine the reachability of the remote objects they point to.  This means the developer will be able to steer the gc proccess and accomodate the requirement of the applications by means of annotating the remote references.
+Semi-automatic garbage collection is a hybrid approach which relies on an underlying local GC and proposes a non-transparent DGC. The approach can be seen as an extension to the indirect reference counting (Piquer,1991) and network objects (Birrell et al.m 1993) since it also maintains the distributed inverse reference graph (IRG) where each remote object keeps a list of pointers to other devices which have references to it. The IRG is augmented with additional semantic information attached to the remote references to help the collector to determine the reachability of the remote objects they point to.  This means the developer will be able to steer the gc proccess and accomodate the requirement of the applications by means of annotating the remote references.
 {{ remoterefint.jpg?430x250 }}
-Since devices may not be able to communicate at some point in time, when a remote reference is first allocated both parties in the interaction will establish a contract with the condition under which the reference is useful to the application. Therefore, if one devices becomes inaccessible because of a broken connection, the other one is aware of the conditions in which the inaccessible reference is still valuable. We propose //referencing strategies// as the language support that allows the developer to determine which collection policy will be applied to both source and target of the reference upon disconnection.  From the point of view of the device hosting remote objects, the DGC will be able to determine the reachability of its remote objects based on the analysis of the referencing strategies of the references pointing to them. From the point of view of the clients, the referencing strategy will determine the rebinding policy to apply to a reference after a disconnection.
+Since devices may not be able to communicate at some point in time, when a remote reference is first allocated both parties in the interaction will establish a contract with the condition under which the reference is useful to the application. Therefore, if one devices becomes inaccessible because of a broken connection, the other one is aware of the conditions in which the inaccessible reference is still valuable.
+We propose //referencing strategies// as the language support that allows the developer to determine which collection policy will be applied to both source and target of the reference upon disconnection.  From the point of view of the device hosting remote objects, the DGC will be able to determine the reachability of its remote objects based on the analysis of the referencing strategies of the references pointing to them. From the point of view of the clients, the referencing strategy will determine the rebinding policy to apply to a reference after a disconnection.
 ==== Ongoing and Future work ====