Command Interface Spec

[mappum]

I've been thinking about how to implement a command interface to allow easily adding new functionality that will be accessible through CLI, HTTP RPC, etc. This stuff is important to get right since it's how we will create the interface developers will see when building stuff on top of IPFS, and good UX is a major factor for adoption.

Here's the design document where I've done some preliminary planning: https://gist.github.com/mappum/32cb25c9016ccd0219c8

Feel free to be critical, and write suggestions by forking the gist. If we can agree on a spec, I will quickly start hacking out the implementation.

RFC @jbenet @whyrusleeping @perfmode

[jbenet]

So far thumbs up. addresses most of what i want out of it. Quick notes

• request on HTTP transport should also be able to be done via a JSON POST body too (so both GET using query string params, and JSON POST body. libs should handle this for us)
• docs in markdown are great for web (:+1:), though not sure how well they will turn out for commandline help/man pages. (Oh, now i see your Markdown -> ANSI comment, yeah!)
• love the specifying of options nicely with a structure
• probably mentioned it somewhere but subcommands in http can be /cmd/subcmd/subsubcmd

[whyrusleeping]

How will you do subcommands via RPC?

[btc]

merged! 91fe0d9