[coyotos-dev] Capability Exchange
Jonathan S. Shapiro
shap at eros-os.org
Thu Jun 1 10:42:42 EDT 2006
I am unclear on your question -- at least partly because there exists no
operation to do a content swap anywhere in Coyotos or EROS, so I'm not
sure what you are referring to there.
There is a *proposed* operation to do what I have referred to as an
"object exchange" between space banks. The idea is that two space banks
get together and do an even swap of *ownership* of k objects for k
objects. This doesn't require finding the objects or swapping their
content. It merely requires knowing the *identity* of the objects (which
is stored inside their capabilities and is accessible to space bank via
the range capability). The space bank internally tracks these identities
already so that it knows what to revoke when the space bank is
destroyed.
In the special case where the "k objects" from one side (or both) are
"all of the objects associated with some sub-bank" we can re-parent the
bank as well.
I don't think that any of this relates to rights amplification, but if
you can expand on that part of your question I'll try to respond.
shap
On Thu, 2006-06-01 at 12:33 +0200, Neal H. Walfield wrote:
> How is capability exchange and rights amplification to be done on
> Coyotos? We have discussed, for instance, the mechanism to reparent a
> space bank and the mechanism to swap the contents of two objects
> (effectively reparenting the object). Both of these require taking a
> capability as an argument and finding the associated object. I
> imagine that the interfaces for these mechanisms might looks something
> like this:
>
> reparent (Bank, Descendent)
> swap (Bank, object1, object2)
>
> Given the capability, how does the server find the object?
>
> Thanks,
> Neal
> _______________________________________________
> coyotos-dev mailing list
> coyotos-dev at smtp.coyotos.org
> http://www.coyotos.org/mailman/listinfo/coyotos-dev
More information about the coyotos-dev
mailing list