research:dgc
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
research:dgc [2006/07/01 12:42] – elisag | research:dgc [2006/07/01 13:36] – elisag | ||
---|---|---|---|
Line 1: | Line 1: | ||
+ | ===== Distributed Garbage Collection ===== | ||
==== Motivation ==== | ==== Motivation ==== | ||
Line 10: | Line 11: | ||
==== 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, | + | 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, |
- | Our approach propose that remote references will be tangible to the developer who will determine the conditions under which a reference is meaningful to the application in order to help the collector to ascertain if the remote object they point to can be reclaimed. 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 then 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. That is why we talk about remote reference as two party contract since both parties in the interaction know exactly the disposability of a reference after a disconnection without requiring later communication. | + | {{ remoterefint.jpg?430x250 }} |
- | We propose // | + | 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. |
==== Ongoing and Future work ==== | ==== Ongoing and Future work ==== | ||
- | We are currently exploring the necessary referencing strategies for the developer to annotate remote references with the extra semantic information. We have come up with a tentative classification of referencing strategies that can be found with more detail | + | We are currently exploring the necessary referencing strategies for the developer to annotate remote references with the extra semantic information. We have come up with a tentative classification of referencing strategies that can be found [ [[http:// |
We have also identified a number of open issues that are not properly tackled yet by our approach: | We have also identified a number of open issues that are not properly tackled yet by our approach: |
research/dgc.txt · Last modified: 2015/02/04 19:10 by elisag