[
https://issues.apache.org/jira/browse/ZOOKEEPER-1346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14059162#comment-14059162
]
Raul Gutierrez Segales commented on ZOOKEEPER-1346:
---------------------------------------------------
Added some more comments on the reviewboard, mainly questions about diverging
impls in the Netty vs NIO ServerCnxnFactory and smaller nits. Oh, and one more
case in which I think a well defined defined class is better than Map<> for
returning values.
After that I am happy to +1 this. Thanks [~bhavanki]!
> 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.5.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)
