[
https://issues.apache.org/jira/browse/ZOOKEEPER-809?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrei Savu updated ZOOKEEPER-809:
----------------------------------
Attachment: ZOOKEEPER-809.patch
SPEC.txt
This patch contains:
* basic support for sessions ( create: POST
/sessions/v1?op=create&expire=SECONDS, delete: DELETE /sessions/v1/<ID>,
heartbeat: PUT /sessions/v1/<ID> )
* support for ephemeral nodes: create: POST
/znodes/v1/a/b?op=create&name=c&ephemeral=true&session=ID
* experimental (almost complete) python REST client
* demos: demo_master_election.py & demo_queue.py
* updated specs
I'm not going to implement watches now because they are not useful if the
client pulls the server for changes.
Working on:
* configuration, ACLs and basic authentication
* packaging - I want to be able to run the REST gateway as a task managed by
the Hue [1] supervisor.
I would really like to get more feedback from you regarding this patch. Thanks.
[1] http://github.com/cloudera/hue
> Improved REST Interface
> -----------------------
>
> Key: ZOOKEEPER-809
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-809
> Project: Zookeeper
> Issue Type: Improvement
> Components: contrib
> Reporter: Andrei Savu
> Assignee: Andrei Savu
> Attachments: SPEC.txt, SPEC.txt, ZOOKEEPER-809.patch
>
>
> I would like to extend the existing REST Interface to also support:
> * configuration
> * ephemeral znodes
> * watches - PubSubHubbub
> * ACLs
> * basic authentication
> I want to do this because when building web applications that talks directly
> to ZooKeeper a REST API it's a lot easier to use (there is no protocol
> mismatch) than an API that uses persistent connections. I plan to use the
> improved version to build a web-based administrative interface.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
