[
https://issues.apache.org/jira/browse/ZOOKEEPER-74?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12654670#action_12654670
]
Krishna Sankar commented on ZOOKEEPER-74:
-----------------------------------------
Couple of quick questions:
a) Do we want to go the route of refactoring the code from a few UML and
sequence diagrams or just wing it ?
b) As you guys know the code better, what is the approx effort involved ? Is it
a question of cleaning up the object graph (creation et al) or more involved ?
c) What is the time frame for 3.2.0 ? Looks like we couldn't do it in 3.1.0
timeframe.
d) And as Ben poits out, we need to complete the patches in flight even before
looking at refactoring.
Cheers
<k/>
> Cleaning/restructuring up Zookeeper server code
> -----------------------------------------------
>
> Key: ZOOKEEPER-74
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-74
> Project: Zookeeper
> Issue Type: Improvement
> Components: server
> Reporter: Mahadev konar
> Assignee: Mahadev konar
> Fix For: 3.2.0
>
>
> I have been thinking this for a while and find that the zookeeper server code
> needs some cleaning up. The server code is a little tricky/confusing to read
> sometimes gievn that there is no clearity on ownership of objects. I will put
> down a proposal for restructuring/cleaning the code up with javadocs so that
> the code is easier to understand and develop on. comments on what you find
> confusing are welcome on this jira.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
