Patrick Hunt commented on ZOOKEEPER-364:

ZOOKEEPER-36 allows for REST based tools to be developed. however this is 
as a proxy, rather than a core part of the server. so I don't think we should 
rely on rest for
implementing clients (at least default CLI), even though things like python 
work really well (there's an example tree dumper as part of 36)

Also implementing in Java seems to result in significant overhead - ie starting 
a jvm for each command execution.

Perhaps C? Similar to the cli.c we currently have, but a set of command line 
tools rather than a 
shell. I'm not sure c would be my first choice, but it would be nice from the 
perspective of
exercising/testing our c binding.

Perhaps Perl? Chris has done a great job with the perl binding... however that 
would put
a requirement on external toolset not shipped with the release (cpan).

Perhaps some other lang, like python? Basically this forces us to implement 
python bindings
on top of the c intf. So the benefits of exercising c, plus we get python 
binding, plus the
benefits of implementing the commands using a scripting lang?

> command line interface for zookeeper.
> -------------------------------------
>                 Key: ZOOKEEPER-364
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-364
>             Project: Zookeeper
>          Issue Type: New Feature
>    Affects Versions: 3.0.0, 3.0.1, 3.1.0, 3.1.1
>            Reporter: Mahadev konar
>             Fix For: 3.2.0
> currently we have a shell based interface for zookeeper (which again isnt 
> well published). we should have a well published cli based interface for 
> zookeeper.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

Reply via email to