[
https://issues.apache.org/jira/browse/ZOOKEEPER-1346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13509551#comment-13509551
]
Ted Dunning commented on ZOOKEEPER-1346:
----------------------------------------
Regarding resty-ness, I think that this interface is a real candidate for not
using the GET/PUT/POST/DELETE verb at all but simply post-pending a verb to the
URL of appropriate report. For that matter, the available verbs could be added
to each report for convenience if there is an HTML view.
This allows <mumble>/<connection>/close which is much more clearly
self-documenting than a guess about what different operations might do to the
connection in question.
> 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.2.patch, 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
