You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@zookeeper.apache.org by "Thomas Koch (JIRA)" <ji...@apache.org> on 2018/06/14 19:43:00 UTC

[jira] [Assigned] (ZOOKEEPER-1287) DataTree deserialization methods should return DataTree instance

     [ https://issues.apache.org/jira/browse/ZOOKEEPER-1287?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Thomas Koch reassigned ZOOKEEPER-1287:
--------------------------------------

    Assignee:     (was: Thomas Koch)

> DataTree deserialization methods should return DataTree instance
> ----------------------------------------------------------------
>
>                 Key: ZOOKEEPER-1287
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1287
>             Project: ZooKeeper
>          Issue Type: Sub-task
>            Reporter: Thomas Koch
>            Priority: Minor
>
> There are a couple of deserialization methods that all receive a new DataTree instance as parameter forwarding this instance in a row until the last in the row populates this instance. While this pattern is derived from jute there's no reason not to instantiate a new DataTree object in the last deserialization method and returning it through the stack. That makes it easier to reason about the code because it then is obvious that the DataTree instance worked on is indeed a new instance.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)