<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div dir="ltr">Note: if the Day is a local, near object, then new day will be the resolution, if not already so. A different #ewhen: #then: sendERefTo: block would be provided. So for tomorrow, esseDay6 is not an instance of ENearRef, it’s the concrete object itself.</div><div dir="ltr"><br></div><div dir="ltr">For today we’ll see Alice’s #greet: message she sends to Bob, when she gets the #meet: message from Carol. </div><div dir="ltr"><br></div><div dir="ltr">As the same from when Carol sends to Alice, as the message gets encoded through the Scope (holding the four tables) exactly the samesame. The message is sent to the FarRef registered in the Answers table. We see two variations, implicitly, for how these FarRefs (1 are in the Answers table…</div><div dir="ltr"><br></div><div dir="ltr">A) the initial references to Alice & Bob, held by Carol are the Answers to Carols’ two #lookup: calls to her Introducer. They are only resolved if successfully connected. </div><div dir="ltr">B) the reference to Bob, held be Alice was the result of a #provideFor: nonce / #acceptFrom: nonce exchange through Bob. These are wire Nonces, a link between remote objects within the pipe, the connected/encrypted session. Wires through Pipes.</div><div dir="ltr"><br></div><div dir="ltr">Anyhow, the Promise in Alice, which is the promise with the resolver attached to the message #greet: over the Bob’s Session. Is regretted in the adjacent Imports table. Both Answers (Orange) and Imports (Burgundy) hold the promise / FarRef side of remoting. </div><div dir="ltr"><br></div><div dir="ltr">Looking over at what happened in Alice as she exported & got a question, are entries in her Questions (Yellow) and Exports (Pink). Note that these are both</div><div dir="ltr"><br></div><div dir="ltr">There are two sets of mono-directional referencing. Questions (Yellow) are objects out to Answers (Orange) [Y -> O] and Exports (Pink) are out to Imports (Burgundy) [P -> B]. </div><div dir="ltr"><br></div><div dir="ltr">That’s down-range: [YO , PB]! These two mono-directional reference sets are attached cross-range, by direction: Outz are Questions and Exports [YP] and Inz are Answers and Imports [OB].</div><div dir="ltr"><br></div><div dir="ltr">That’s 2 in one direction, let’s add two more flipped so the one with out refs can also have I Z refs. </div><div dir="ltr"><br></div><div dir="ltr">AndsoWe can see each side of the Session has a Scope with 4 tables, from a couple of , flipped pairs of refs: Outz and Inz. So our Scope contains [YP , OB], [Outz , Inz].</div><div dir="ltr"><br></div><div dir="ltr">The third little wire is going out Carol’s Questions and in the Answers in Alice. This is the RemoteResolver to Carol’s promise which is the result of sending a message, out to Alice.</div><div dir="ltr"><br></div><div dir="ltr"><img alt="image0.jpeg" src="cid:138DA923-8FF8-4EE2-A778-4F29F71EE61B"><br><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"><p>Now we see the #greet: message #realized: in Bob. In his Scope, we’ve got the entry in Bob’s Yellow Questions, answered to Alice, out. Then there’s the entry in Bob’s Pink Exports table the promise tail out to Carol’s currency through Alice. Will become resolved. Finally we see the entry in Bobs Orange Answers table the in side of the promise’s resolver. Tak.</p>
<p><img alt="image1.jpeg" src="cid:2F00D7D1-01B5-43EB-9D86-CCCEE6459A70"><br>
</p>
<p><br>
</p>
</div></body></html>