Up again, down again. Another night of troubled dreams. Sigh.

Andso, the next couple of slides. Getting into the business, now.

Now Alice knows the 2nd promise, p2 in Alice pointing to the resolution of the #greet: message in Bob is resolving the p1 promise in Carol. So we have one promise p1, being resolved to a 2nd promise p2. So Alice knows p2 is transferring and so she sends a #provideFor: to prepare the transfer of p2 to Carol. As shown it can be seen to provide the reference to the result of the message send, not a reference to Bob as in our previous transfer. No, we are transferring a promise this time, useful to think of as a future reference to a resolved object. It will become an object upon resolution of #greet:.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image0.jpeg
Type: image/jpeg
Size: 261900 bytes
Desc: not available
URL: <http://lists.squeakfoundation.org/pipermail/squeak-dev/attachments/20221021/d8b1c018/attachment-0002.jpeg>
-------------- next part --------------


Here we see the little teensie #whenMoreResolved sent back to Carol to the resolver of p1 with a reference to the tail end of p2 in Bob and the transfer is in-process.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: image1.jpeg
Type: image/jpeg
Size: 263695 bytes
Desc: not available
URL: <http://lists.squeakfoundation.org/pipermail/squeak-dev/attachments/20221021/d8b1c018/attachment-0003.jpeg>
-------------- next part --------------


—
Have a good one; keep it, light.
Kindly, langohr . .. … ‘…^,^ 🐇🐇🐇

Sent from Callisto House Mobile - Europa 
:: decentralized mobile homeless solutions ::

> On Oct 20, 2022, at 12:28, rabbit <rabbit at callistohouse.org> wrote:
> 
> Guten Morgen, mein Damen und Herren! The second message has been ingested by Alice. All Scope entries of same correspondence.
> 
> <image0.jpeg>
> 
> 
> Here we see the tiny #whenMoreResolved:, in Alice, referencing the remote resolver in Carol for the first promise. This tiny message is invoked with the reference to the promise for a resolution in Bob, the promise for the #greet: call to Bob from Alice’s #meet: message. This resolution for the secondary promise will do ‘promise shorting’ and will result in Carol’s first promise pointing to Bobb, as Alice is no longer involve. Wait and see! ;)
> 
> <image1.jpeg>
> 
> 
> —
> Have a good one; keep it, light.
> Kindly, langohr . .. … ‘…^,^ 🐇🐇🐇
> 
> Sent from Callisto House Mobile - Europa 
> :: decentralized mobile homeless solutions ::
> 
>> On Oct 18, 2022, at 07:41, rabbit <rabbit at callistohouse.org> wrote:
>> 
>> Alright, Howz everyone? I took a day to work on my vintage ride…so I sent #pauseDay to the esseDay6 promise.
>> 
>> Now we will see promise chaining as Carol sends a 2nd message to the promise resolution (p1) of the initial send to Alice, which was resolved to the promise from sending a message to Bob. The resolution to the initial promise will occur in Bob.
>> 
>> ———- Scope tables ———-
>> Outz:
>> - Questions (Yellow)
>> - Exports (Pink)
>> Inz:
>> - Answers (Orange)
>> - Imports (Burgundy)
>> 
>> Carol sends 2nd message #isAllWell to the result of #meet: which is now the result of #greet:…
>> 
>> <image0.jpeg>
>> 
>> 
>> 
>> The 2nd message is forwarded to Alice for the initial msg send. All the same Scope entries are made:
>> 
>> - p2 reference (r3’) is IN in Carol’s table Imports (Burgundy)
>> - remote resolver to p2 is OUT in Carols Questions (Yellow)
>> <image1.jpeg>
>> 
>> 
>> —
>> Have a good one; keep it, light.
>> Kindly, langohr . .. … ‘…^,^ 🐇🐇🐇
>> 
>> Sent from Callisto House Mobile - Europa 
>> :: decentralized mobile homeless solutions ::
>>