[
https://issues.apache.org/jira/browse/ZOOKEEPER-1346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13499296#comment-13499296
]
Skye Wanderman-Milne commented on ZOOKEEPER-1346:
-------------------------------------------------
The javadoc for the AdminServer class goes over the URLs, but this should
probably be in the actual docs too. I'll update them once everything is
finalized. There's really only two URLs right now: /command (lists all the
commands), and /command/<command> (runs <command>). I'm open to suggestions for
how to change this, including how to make it more REST-y :)
I like the idea of supporting further URL hierarchies. This would probably
require changing how the server turns URLs into Commands... maybe a command can
be registered with a name like "session/*" or "session/<id>" and the server can
fill in what was actually requested? I would have to think about it. This is
probably something to work on after all the basic functionality is implemented
to make sure we don't complicate things too much.
Right now I'm focusing on reimplementing the current 4lw functionality, but I
definitely would like to add new functionality, including the ability to make
changes to the ZK server. I'll check out what the JMX metrics are. On this
note, I'd also like to support authentication and encryption (again, after the
basics are in place).
> Handle 4lws and monitoring on separate port
> -------------------------------------------
>
> Key: ZOOKEEPER-1346
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1346
> Project: ZooKeeper
> Issue Type: Improvement
> Components: server
> Reporter: Camille Fournier
> Assignee: Skye Wanderman-Milne
> Fix For: 3.5.0
>
> Attachments: ZOOKEEPER-1346_jetty.patch, ZOOKEEPER-1346.patch
>
>
> Move the 4lws to their own port, off of the client port, and support them
> properly via long-lived sessions instead of polling. Deprecate the 4lw
> support on the client port. Will enable us to enhance the functionality of
> the commands via extended command syntax, address security concerns and fix
> bugs involving the socket close being received before all of the data on the
> client end.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
