Chris Darroch commented on ZOOKEEPER-36:
I took a quick look at the spec; nice! I like that it follows the spirit of
the HTTP spec in the way I envisioned. A couple of minor thoughts:
I think it would be nice to avoid POST entirely, if only because POST is so
over-used that it no longer has any particular meaning except "send stuff to
server". Suppose you used the trailing slash in the URI to distinguish
meanings? Having hacked on mod_dir at various points this occurs to me as a
possibility. For example:
PUT /foo -> zoo_set(/foo)
PUT /foo/ -> zoo_create(/foo)
The same would work to overload GET:
GET /foo -> zoo_get(/foo)
GET /foo/ -> zoo_get_children(/foo)
I especially like the GET cases because they correspond nicely to how URIs are
mapped to files and directories.
As for running code, I'm working (slowly) on a mod_zookeeper and you'll be the
first to know if I get it to a releasable state. The basic purpose is similar
to mod_dbd: provide connections that other modules can use however they choose.
> 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.
This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.