[cap-talk] Last Call for ref_send API 1.0

[Dean Tribble]

BTW A general point:  since the security review write-up is in progress, you
might consider waiting until the write-up is complete before publishing.
There's alsways a few things that won't get articulated until the document
is in writing that you may want to address.

On 4/4/07, Kevin Reid <kpreid at mac.com> wrote:
>
> Question: What does Eventual#ready do? The documentation and example
> don't make it clear what the difference between its input and its
> output are.
>
> Question: The documentation does not state explicitly that a resolved
> Promise will (allegedly) from then on return the same value from
> every call to cast(). Is this the case?
>
> Comment: E-on-Java provides Ref.makeSwitchablePromise, which has a
> somewhat similar effect to ref_send's Volatile (if I understand it
> correctly). <http://www.erights.org/javadoc/org/erights/e/elib/ref/
> Ref.html#makeSwitchablePromise(java.lang.Object)> This behavior can
> also be built out of the proxy protocols (EProxyResolver/makeProxy).
>
> What I am hoping for is that ref_send will have semantics which are
> close enough to E's that a program built on ref_send can
> transparently communicate with a program built on ELib (possibly
> requiring a vat boundary between them).
>
> --
> Kevin Reid                            <http://homepage.mac.com/kpreid/>
>
>
> _______________________________________________
> cap-talk mailing list
> cap-talk at mail.eros-os.org
> http://www.eros-os.org/mailman/listinfo/cap-talk
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.eros-os.org/pipermail/cap-talk/attachments/20070405/45146273/attachment-0001.html