[
https://issues.apache.org/jira/browse/ZOOKEEPER-16?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12668995#action_12668995
]
Mahadev konar commented on ZOOKEEPER-16:
----------------------------------------
i think the we should avoid doing more work at the server and let the client
handle the path checking. Doing this check in the PrepRequestPRocessor will
have performance impact. On the other hand we could do some minor chekcing on
the server to see if the path is null, starts with / and others...
we can open up another jira for path validation on server side if you feel
strongly abt it.
for 2)
their should be some client c libarary that should catch unicode characters ..
again we can open another jira for that. for now we can go with this...
> Need to do path validation
> --------------------------
>
> Key: ZOOKEEPER-16
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-16
> Project: Zookeeper
> Issue Type: Bug
> Components: c client, java client, server
> Affects Versions: 3.0.0, 3.0.1
> Reporter: Patrick Hunt
> Assignee: Patrick Hunt
> Fix For: 3.1.0
>
> Attachments: ZOOKEEPER-16.patch, ZOOKEEPER-16.patch,
> ZOOKEEPER-16.patch
>
>
> Moved from SourceForge to Apache.
> http://sourceforge.net/tracker/index.php?func=detail&aid=1963141&group_id=209147&atid=1008544
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
