cli client intended for direct use by humans, and also in scripts, with the general goal of interacting with parties and their data in the same fashion as Pads and Bots. Initial target use case : development and debugging.
Some motivating examples:
[ ] Join a given party, verify connection succeeds to at least one peer
[ ] Join a given party and dump available party info (available peers, presence data, ??)
[ ] Ping specific peers, report response
[ ] List data items on party
[ ] Dump data item content matching query, raw messages
[ ] Dump data item content matching query, CRDT reconstructed state
[ ] Introduce mutations to data
[ ] List party members (from admit credential messages)
[ ] Verify party content availability
...
User interface in the spirit of redis-cli (repl/interactive mode, single command mode, pipe input to stdin)
Thin wrapper over wireline-core/dxos modules, same architecture as bots/launchpad.
richburdon
commented
4 years ago
cli client intended for direct use by humans, and also in scripts, with the general goal of interacting with parties and their data in the same fashion as Pads and Bots. Initial target use case : development and debugging.
Some motivating examples:
User interface in the spirit of redis-cli (repl/interactive mode, single command mode, pipe input to stdin)
Thin wrapper over wireline-core/dxos modules, same architecture as bots/launchpad.
List of proposed commands and syntax:
party examineparty joinpeer ping...TODO(): review, discuss, complete this spec.