[cap-talk] Reference count based garbage collection seen as flawed
smagi at higherlogics.com
Wed Jan 4 12:14:23 PST 2012
On 1/4/2012 2:03 PM, David Barbour wrote:
> Treating all objects as local causes problems due to conditions of
> disruption and indeterministic latency.
You can isolate remote references behind an abstraction that only
exposes methods that don't have disruption/latency problems. Something
like E's reference semantics:
Other options are mobile code, but the above distinction integrates well
with current languages, and mobile code does not.
More information about the cap-talk