[
https://issues.apache.org/jira/browse/ZOOKEEPER-1346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13468901#comment-13468901
]
Henry Robinson commented on ZOOKEEPER-1346:
-------------------------------------------
+1, great idea.
I do think it's important that we set out with the intention of deprecating the
old protocol eventually. This is a good opportunity to properly establish a
procedure for doing that. I suggest including both in the next major release
(3.5?) and warning that the old protocol will be turned off in 3.6. Assuming
all goes according to plan, we can eventually ship 3.6 with only a Jetty-based
4lw implementation.
> 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: Camille Fournier
> Fix For: 3.5.0
>
> Attachments: ZOOKEEPER-1346_jetty.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
