[cap-talk] Capability levels - transparent network extension, no encryption

[David Hopwood]

David Hopwood wrote:
[...]
> There must be a mechanism to create a new object at the network level,
> assigning it a new capability representation (YURL, etc.) So just create
> a new network object with the behaviour of forwarding to the local object.
> This is often called a "scion" or "skeleton". Various optimizations are
> possible -- cacheing so that there is at most one scion per local object,
> shortening chains of scions and "stubs" (proxies), etc. A variant that
> also supports object migration and acyclic distributed GC is described
> in:
> 
>   M. Shapiro, P. Dickman, and D. Plainfossé
>   SSP Chains: Robust, Distributed References Supporting Acyclic Garbage
>   Collection. Technical Report 1799, Institut National de la Recherche
>   en Informatique et Automatique, Rocquencourt, France, 1992.
>   <http://www-sor.inria.fr/publi/SSPC_rr1799.html>

I should point out that most of the complexity of the protocol in this paper
is due to supporting fault tolerance and object migration, not due to the
issue that Jed raised.

-- 
David Hopwood <david.nospam.hopwood at blueyonder.co.uk>