I think Module imports and parent, vat pending continuations and vatSemaphores and scope-encrypted wiring and running priority stacks and the tuners agents, the transceivers, all are managed through an eTupleSpace as the roots of storage with ephemeral registration in module definitions. Chain a break reactor to uncouple. I am not sure how this rests in design, a start to integrate with tracing added. Welcoming comments. These thoughts to prep for ASN1 to substitute through the scope, or through eLinda.




- Alan
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.squeakfoundation.org/pipermail/squeak-dev/attachments/20171016/88fe41f2/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: IMG_1807.jpg
Type: image/jpeg
Size: 35041 bytes
Desc: not available
URL: <http://lists.squeakfoundation.org/pipermail/squeak-dev/attachments/20171016/88fe41f2/attachment.jpg>