[
https://issues.apache.org/jira/browse/ZOOKEEPER-36?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12699890#action_12699890
]
Patrick Hunt commented on ZOOKEEPER-36:
---------------------------------------
Chris thanks for reviewing this. In particular I think it's important both for
users as well as implementors (interop) to have a clear spec.
/foo and /foo/ were considered, but imo this is pretty hacky and prone to error
(both user and potentially intermediate actors like proxies...) Perhaps my
search background showing through - url canonicalization often ignores the
trailing slash.
/foo and /foo/* were also considered, this is a bit better imo (you might also
support things like /foo/*/bar, yikes! :-) )
EOD I think it makes more sense to be explicit. it's not as "clean" but it
allows us to follow
the HTTP spec and it's more obvious what's going on when reading the client
code that uses the REST service (even if you haven't read the spec
"view=children" is going to be more obvious than trailing/non-trailing slash).
> REST access to ZooKeeper
> ------------------------
>
> Key: ZOOKEEPER-36
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-36
> Project: Zookeeper
> Issue Type: New Feature
> Components: contrib
> Reporter: Patrick Hunt
> Assignee: Patrick Hunt
> Fix For: 3.2.0
>
> Attachments: rest_2.tar.gz, SPEC.txt
>
>
> Moved from SourceForge to Apache.
> http://sourceforge.net/tracker/index.php?func=detail&aid=1961763&group_id=209147&atid=1008547
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
