[
https://issues.apache.org/jira/browse/ZOOKEEPER-849?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12965437#action_12965437
]
Benjamin Reed commented on ZOOKEEPER-849:
-----------------------------------------
for the server we really want to avoid the overhead of object creation and
memory footprint, so we really do want to be working with raw bytes. the idea
is to validate the bytes at the beginning of the pipeline and then just use the
raw bytes for the rest of the time.
i think we should get consensus that we want to change the client APIs to use a
Path object, and then on the methods of that object before we forge ahead on
this one. the sequential flag is a particularly ugly piece. for example are
zk.create(new Path("/a/", true), data, acl, CreateMode.PERSISTENT_SEQUENTIAL)
and zk.create(new Path("/a/b", false), data, acl,
CreateMode.PERSISTENT_SEQUENTIAL) both valid? what about zk.create(new
Path("/a/b", true), data, acl, CreateMode.PERSISTENT)?
> Provide Path class
> ------------------
>
> Key: ZOOKEEPER-849
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-849
> Project: ZooKeeper
> Issue Type: Sub-task
> Components: java client
> Reporter: Thomas Koch
> Assignee: Thomas Koch
> Fix For: 3.4.0
>
> Attachments: ZOOKEEPER-849.patch, ZOOKEEPER-849.patch
>
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
