Problem: Commands like endo make counter.js --name counter implicitly create a unique worker for the counter. This makes it impossible to address the worker for follow-up commands, like an eval co-located with the counter.
This change introduces an undeniable INFO name to all hosts that allows the host to address the values used to create pet named values. For example, INFO -> counter -> worker addresses the worker that was used to create counter. Until we have pet name path lookup (#1915), you need multiple invocations of E() to perform of depth greater than 1, for example:
Problem: Commands like
endo make counter.js --name counter
implicitly create a unique worker for the counter. This makes it impossible to address the worker for follow-up commands, like aneval
co-located with thecounter
.This change introduces an undeniable
INFO
name to all hosts that allows the host to address the values used to create pet named values. For example,INFO -> counter -> worker
addresses the worker that was used to createcounter
. Until we have pet name path lookup (#1915), you need multiple invocations ofE()
to perform of depth greater than 1, for example:This facility is intended to compose well with follow-up changes for inspecting a worker’s log or copy one of these “unnamed” capabilities to a name.