Command line routing and routines

[respect]

Command line routing and routines

[augustohp]

This should be moved/mentioned in the Cli component and closed here, should't it?!

[alganet]

I don't know yet. I've always though on Cli as a command line interface for Config. Maybe we should move Cli to Config or Foundation.

Cli responsibility is spread, hard to tell where things must go.

[alganet]

I'm willing to do this. There are a couple of things to figure out before then:

• The path and method can be abstracted as words: get users alganet == GET /users/alganet
• Query string options can be abstracted as getopts get users --since=2009 == GET /users/?since=2009, though Respect\Rest will not abstract that for you. You'll need to do that on the route implementation. Additional ->env("cli"), ->env("http" and ->env("cgi" can be added as routines to improve abstraction without increasing coupling.
• Mime negotiation could be abstracted to bash negotiation or something like this. Language negotiation can be done using env vars. A lot of thinking on how that could work is needed.

Just to make clear: this issue doesn't cover transparent HTTP/bash mapping. It allows developers to do that by providing tools to serve content in both HTTP and bash, as they're both RESTful.