Open rekmarks opened 7 months ago
endo rename
should be replaced with endo mv|move
when we can support dot delimited paths, and we should support dot delimited paths for both the source and target. We should also guarantee that a move occurs in a single JavaScript event unless the dot-delimited path reaches outside the local dæmon. That will require the move
operation to walk from formula to formula for both the source and target path before falling through to the lookup
protocol. We will need a corresponding protocol for “depositing” a formula identifier to the target “directory” and allow that protocol to work remotely.
E(remoteDirectory).deposit(name, nonce, addresses)
. See https://github.com/ocapn/ocapn/pull/105
The local behavior occurs if the nonce exists in the daemon and just writes the corresponding name and formula identifier to the local pet store (directory). Otherwise, the remote behavior is to create a “remote” formula that captures the nonce and addresses. So, if the remote restarts, it can reestablish a connection to the node that the nonce calls home.
Following #2022, we should support dot-delimited petname paths in the CLI such that wherever a petname for an existing value is provided, a path can be provided instead. This path will then be passed to the mailbox
lookup
method, which will attempt to resolve the value.For example, this should work:
Note that the
parsePetNamePath()
utility should be used for dot-delimited path parsing in the CLI.See also discussion in #1915.
TODO
eval
#2034cancel
--as
https://github.com/endojs/endo/pull/2047dismiss
inbox
list
reject
make
#2281store
#2281adopt
#2325bundle
#2296cat
#2296dismiss
follow
#2296install
#2325mkdir
#2325mkguest
mkhost
move
#2227open
#2296reject
remove
#2325request
#2325resolve
run
#2296send
show
#2237spawn
#2325N/A
clean
help
log
purge
restart
start
stop
ping
where