[
https://issues.apache.org/jira/browse/ZOOKEEPER-1346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14050232#comment-14050232
]
Bill Havanki commented on ZOOKEEPER-1346:
-----------------------------------------
Hi all,
After syncing up with Skye, I rebased the latest patch here (#8) against trunk.
Since it's been well over a year since there was activity here, and the rebase
wasn't clean, I'd like to submit the changes for fresh review.
Does anyone have a preference for whether I submit it all as a single patch
here, or break it up into several smaller patches for easier consumption?
Personally, I prefer more, smaller patches, and I'd be happy to post them under
subtasks to this JIRA for tracking purposes.
I can also use Review Board (reviews.apache.org) for posting and soliciting
feedback, if the project uses that.
Thanks!
Bill
> 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: Bill Havanki
> Fix For: 3.6.0
>
> Attachments: ZOOKEEPER-1346.2.patch, ZOOKEEPER-1346.3.patch,
> ZOOKEEPER-1346.4.patch, ZOOKEEPER-1346.6.patch, ZOOKEEPER-1346.7.patch,
> ZOOKEEPER-1346.8.patch, ZOOKEEPER-1346.patch, 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 was sent by Atlassian JIRA
(v6.2#6252)
