(I'm waiting for my password reset to the ASF JIRA so I thought I'd
comment here in the mean time...)

Maven has a nice directory layout structure that takes into account
multiple languages, e.g., src/main/java, src/main/c, etc.

I really dislike the terms recipes and contrib for a collection of
high-level implementations that people will rely upon. Recipes don't
sound like code, they sound like documentation to me. Do you ever
really use contrib code directly in your programs? Usually one copies
it and modifies it, like the classic petstore web app, rather than
linking directly against it. I think if there are going to be
implementations of the recipes then these should have a name, rather
than being pushed into some contrib bucket that gives the impression
that it's take-it-or-leave-it code.

Something like zookeeper-commons or ...?

.. Adam

On Fri, Jan 16, 2009 at 11:22 AM, Benjamin Reed <> wrote:
> This is exactly what we want. ZooKeeper was designed to provide kind of a 
> coordination micro-kernel. the idea is that all sorts of more specialized 
> primitives can be built at the client, thus keeping the core server simple 
> and manageable.
> unfortunately, the thing that is holding us back is the directory structure. 
> in some sense it's pretty silly, but we need a nice way to organize the 
> recipe specifications and implementations so that multiplatform 
> implementations will be compatible and users can understand the semantics. 
> See ZOOKEEPER-80. Once that gets fixed we have a lock recipe, keptset recipe, 
> and there is a file monitoring library that is ready to go in.
> the key to ZOOKEEPER-80 is to fix the structure and the build process.  if 
> you have a flash inspiration on how to best implement ZOOKEEPER-80, we are 
> all ears.
> ben
> ________________________________________
> From: Tom Nichols []
> Sent: Friday, January 16, 2009 6:54 AM
> To:
> Subject: Standard redistributable set of primitives?
> Hi,
> I was wondering if there were plans to create a set of standard
> ZooKeeper primitives, sort of like commons-collections.  I figure it
> would be mostly based off of the recipes on the ZK wiki, but it would
> provide users with a slightly easier starting point, not to mention it
> would be well-tested and prevent users avoid "re-inventing the wheel."
>  Does this sound like a reasonable idea?
> Thanks.
> -Tom

Reply via email to