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

Rob Withers <[email protected]> Sun, 08 Mar 2015 08:33:06 -0600
Newsgroups	gmane.comp.lang.e.general
Message-ID	<[email protected]>
--===============3335152173995433745==
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

<html>
  <head>
    <meta content=3D"text/html; charset=3Dwindows-1252"
      http-equiv=3D"Content-Type">
  </head>
  <body bgcolor=3D"#FFFFFF" text=3D"#000000">
    I had not realized I had posed such a challenging situation.=A0 In
    mulling over what needs to happen, I think the followOn message send
    (#hashCode) needs to be a 3-vat situation, <b>of the Resolver</b>,
    to prevent GC.=A0 Here are the steps I think are needed, #6 being the
    point where my system is failing, due to its absence? <br>
    <ol>
      <li>Carol sends #redirectForTheAnswer to Alice::GalaxyObject with
        a ref to Bob::GalaxyObject, returning a RemotePromise1</li>
      <li>Carol sends #hashCode to the RemotePromise1 from the first
        send, which forwards to the Promise in Alice, where it is
        queued.<br>
      </li>
      <li>3-way: Carol sends a ProvideFor to Bob and Alice sends an
        AcceptFrom to Bob, so Alice resolves Bob::GalaxyObject.</li>
      <li>Alice::GalaxyObject, under computation of
        #redirectForTheAnswer, sends #getTheAnswer to Bob::GalaxyObject,
        returning a RemotePromise2, in Alice, from
        #redirectForTheAnswer.</li>
      <li>The pending #hashCode send is sent to the RemothePromise2, in
        Alice, which points to Bob.</li>
      <li>3-way: In Alice, the redirected #hashCode ought to become a
        3-way for the
        Resolver in Carol, for the intial #hashCode send.=A0 Alice would
        send a ProvideFor to Carol, for that Resolver and Bob would send
        an AcceptFrom to Carol to gain a FarRef to the Resolver.</li>
      <li>Bob::GalaxyObject, under computation of #hashCode, returns the
        value 42.</li>
      <li>Bob sends the pending #hashCode to 42, and resolves the gift
        Resolver. </li>
    </ol>
    I believe the tricky thing is that it is the Resolver which is
    gifted, so it's a different export "polarization" of the minigraph
    for a remote send that has been forwarded. <br>
    <br>
    Thank you,<br>
    Robert<br>
    <br>
  </body>
</html>

--===============3335152173995433745==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
e-lang mailing list
[email protected]
http://www.eros-os.org/mailman/listinfo/e-lang

--===============3335152173995433745==--