[
https://issues.apache.org/jira/browse/ZOOKEEPER-1346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13507913#comment-13507913
]
Nikita Vetoshkin commented on ZOOKEEPER-1346:
---------------------------------------------
About ReST'inness. I think it should be better to prefix this API with
{{/v1/api}} from the start. In ReST with URLs you should provide hierarchy of
resources. In our case we have a collection of command*s* which can look like
this:
{code}
commands/
|-- configuration
|-- connections
|-- connection_stat_reset
|-- dump
|-- environment
|-- get_trace_mask
`-- monitor
{code}
Then, to *get* the {{environment}} one must issue a {{GET}} request to the URL
{{/v1/api/commands/environment}}.
> 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
