[
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
Changes in this patch:
* {{ZooKeeperService}} now uses the servlet context path and not full URI as a
key for retrieving ZooKeeper connections
* added a configuration file: conf/rest.properties
* added support for multiple endpoints: /cluster1, /cluster2 - useful if you
have multiple ZooKeeper clusters
* HTTPS support
* HTTP Basic Authentication
* shutdownHook for cleanup
I'm still working on: packaging, ACLs & ZooKeeper Authentication
I will finish the packaging ant task tomorrow and next week (after the GSoC
"soft" deadline) I will also add support for ACLs and Authentication.
Let me know what you think. Thanks.
> 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,
> 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.
