On Thu, Dec 8, 2011 at 3:08 PM, Christian Schneider <ch...@die-schneider.net
> wrote
>
> karaf uses namings like:
> bundle:list
> service:list
>
> These are resource oriented what means that the scheme bundle references a
> resource type.
The are not exactly resource oriented, I would say the are "feature"
oriented.
Take for example feature:url-list or feature:url-add. The resource oriented
approach would be "feature-url:add and feature-url:list".
And I prefer this logic in camel too.
In general when it comes to commands, I try to think from the
user perspective as much as possible. So I think, the less command scopes,
the easier for the user to use.
i) Less scope = faster code completion (less times the user is
prompted).
ii) Larger number of commands per subshell (the user will have to
switch less between sub shells).
iii) Easier for the user to browse the capabilities of a scope.
Now, regarding the proposal that we should wait, I am ok with it. However,
I don't feel its 100% necessary. As I wrote on the karaf mailing list, the
noun-verb norm would even allow to use nested shells.
So I am not sure that if we adopt the noun-verb norm we will have to change
again (as I don't see how this norm would not be a perfect fit for
subshells).
--
*Ioannis Canellos*
*
FuseSource <http://fusesource.com>
**
Blog: http://iocanel.blogspot.com
**
Apache Karaf <http://karaf.apache.org/> Committer & PMC
Apache Camel <http://camel.apache.org/> Committer
Apache ServiceMix <http://servicemix.apache.org/> Committer
Apache Gora <http://incubator.apache.org/gora/> Committer
Apache DirectMemory <http://incubator.apache.org/directmemory/> Committer
*
