[
https://issues.apache.org/jira/browse/ZOOKEEPER-1346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13499264#comment-13499264
]
Ted Dunning commented on ZOOKEEPER-1346:
----------------------------------------
Skye,
Nice work. Is there documentation about what URL structure you used?
Is there a way to make it a bit more REST-y?
Are there commands that are natural to decompose a bit using a hierarchical URL
style? For instance, if have something that lists live quorum members, it
would be nice be able to append the quorum member id to the URL to get more
details on that member alone. Likewise for live sessions.
Further afield, are there metrics that should be reported/set using this
mechanism? I know that we report a fair number of metrics using JMX, but would
it be good to have a different mechanism?
> 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
