Re: [Zookeeper-user] httpd zookeeper module (experimental)

[Ted D. <tdu...@ve...>]

I have a somewhat similar layer that provides a rest interface for crud
operations on zookeeper via a stateless servlet.

It also provides a simple job queueing interface similar to amazon's SQS.
They idea is that the rest interface does the fancy semantics so exposing
sequential and ephemeral files isn't so important.  In fact, the direct
interface to zoo came about primarily as a debugging and error correcting
layer.  I build this interface using Grails over a weekend or so and it is
turning out very helpful.

I imagine that a number of people are building things like this.  I can
release the file interface part, but would have problems releasing the
entire package.

What sort of semantics would be useful to the community at large?


On 5/1/08 7:23 PM, "Chris Darroch" <ch...@pe...> wrote:

> Hi --
> 
>    I thought I'd post here a quick note about an experimental
> pair of Apache httpd modules I've written, one of which connects
> to ZooKeeper and uses it to provide a robust shared key/value
> storage system.  The other module adds a simple generic HTTP-based
> interface to ZooKeeper and/or several other key/value storage
> providers.
> 
>    These modules are only functional with the unreleased "trunk"
> version of httpd (a.k.a. version 2.4).  Because the common
> "small object cache" provider interface (still under active development)
> only offers simple store/retrieve/delete semantics, some of ZooKeeper's
> most powerful features are unavailable, such as ephermeral and
> sequential nodes.  However, perhaps future work will make these
> more easily integrated (I'm not sure how, though, at the moment).
> 
>    At any rate, for those interested, the modules are at:
> 
> http://people.apache.org/~chrisd/projects/shared_map/
> 
>    There's a longer description of them in this email to the
> httpd-dev mailing list:
> 
> http://mail-archives.apache.org/mod_mbox/httpd-dev/200805.mbox/%3c481A36B2.306
> 09...@pe...%3e
> 
>    Please reply to me with any bugs or suggestions.
> 
> Chris.