Re: Using Vine in 3-way interactions (was Re: Question on redirectors/whenMoreResolved in the 3-way case, in the middle vat)

Hi Mark, please excuse the delay. Among other distractions, I refactored 
my session layer's use of crypto algorithms and added bouncy castle to 
gain AES.  This broke much and I have been trying to recover, with mixed 
results.  Currently, my 3-vat test is still failing so I am unable to 
reproduce this situation, but I wanted to respond.

I think the core issue is that I am not familiar with this notation.  I 
looked at my code and I have the same code: 
https://github.com/tooantuh/pauwau/blob/master/src/main/java/cc/ganymede/pauwau/presentation/lib/handlers/RemoteHandler.java#L133. 
  How should this be notated?

Thank you,
Robert

On 3/22/2015 2:39 AM, Mark Miller wrote:
> Hi Rob, thanks for adding slides. I can now spot the problem -- on your
> transition from slide 15 to 16.
>
> The little blue __whenMoreResolved messages shown do not pass through
> the remote promise in Vat1 on the way to the target in Vat2. Rather, as
> coded at
> <https://github.com/tooantuh/pauwau/blob/f8a49b417a3866b2a3fe9870cc3db82eecf596e0/e-jsrc/net/captp/jcomm/RemoteHandler.java#L139>
>
> when a remote reference (either far ref or remote promise) receives a
> __whenMoreResolved(reactor) message, where the reactor is a remote
> reference (either far ref or remote promise) to a third vat, the
> receiving remote reference acts like a local non-promise -- sending
> itself to the reactor. This is needed for shortening, and is why the
> message is called __whenMoreResolved rather than __whenResolved.
>
>
>
>
> _______________________________________________
> e-lang mailing list
> [email protected]
> http://www.eros-os.org/mailman/listinfo/e-lang
>