research:dgc
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| research:dgc [2006/07/01 15:35] – elisag | research:dgc [2015/02/04 19:10] (current) – elisag | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| ===== Distributed Garbage Collection ===== | ===== Distributed Garbage Collection ===== | ||
| + | [[http:// | ||
| + | |||
| + | < | ||
| + | This page is outdated. Please check [[http:// | ||
| + | </ | ||
| ==== Motivation ==== | ==== Motivation ==== | ||
| Line 9: | Line 14: | ||
| ==== Design ==== | ==== 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. 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,91) and network objects (Birrell et al.,93) 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? | {{ remoterefint.jpg? | ||
| Line 19: | Line 24: | ||
| ==== Ongoing and Future work ==== | ==== Ongoing and Future work ==== | ||
| - | We are currently exploring the necessary referencing strategies for the developer to annotate remote references | + | We are currently exploring the necessary referencing strategies for the developer to annotate remote references. We have come up with a tentative classification of referencing strategies that can be found [ [[http://soft.vub.ac.be/ |
| - | We have also identified | + | There are a number of open issues that are not properly tackled yet by our approach: |
| * Resolving conflicts between client and service provider strategies. | * Resolving conflicts between client and service provider strategies. | ||
| - | |||
| * Indirect references: passing a reference to a third party. | * Indirect references: passing a reference to a third party. | ||
| - | |||
| * Composition mechanism to mark group of remote reference at once. | * Composition mechanism to mark group of remote reference at once. | ||
| - | * Garbage collection of the remote objects once it is no longer pointed to. | ||
| ==== Further Reading ==== | ==== Further Reading ==== | ||
| - | **Semi-Automatic Garbage Collection for Mobile Networks**. Elisa Gonzalez Boix, Tom Van Cutsem, Stijn Mostinckx, Jessie Dedecker, Wolfgang De Meuter, and Theo D' | + | **Semi-Automatic Garbage Collection for Mobile Networks**. Elisa Gonzalez Boix, Tom Van Cutsem, Stijn Mostinckx, Jessie Dedecker, Wolfgang De Meuter, and Theo D' |
research/dgc.1151760944.txt.gz · Last modified: 2006/07/01 15:41 (external edit)