cassandra-client-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Tyler Hobbs <>
Subject Re: Reducing confusion around client libraries
Date Fri, 03 Dec 2010 19:46:34 GMT
Personally, I like the Mongo drivers page:

I like the clear distinction between preferred and alternative clients
without a lot of clutter about release dates and supported versions.  How do
we make that distinction, though?  A "supported by Riptano" section is one
option, but that doesn't even encompass all of the preferred clients.  I
don't know that we have enough active users and maintainers for all of the
languages that we could put up the clients for a democratic vote.

Are client maintainers willing to voluntarily place their clients into
either the "official" list or the "community" list?  Perhaps all clients
should be considered community supported unless selected by, say, the
Cassandra committers as being both up to quality standards and the current
best client for that language.

- Tyler

On Fri, Dec 3, 2010 at 12:18 PM, Nate McCall <> wrote:

> On Fri, Dec 3, 2010 at 11:59 AM, Paul Brown <> wrote:
> >
> > One way that this could be accomplished with a relatively even hand is to
> ensure that the relative liveliness of the client libraries is apparent on
> the page, e.g., a most recent release date, the target language (and
> potentially any additional decoration like Spring or Rails or...), and a
> list of versions of Cassandra supported.
> >
> I agree with Paul - I think some additional "feature" and project
> activity comparison is the way to go near term.
> Nothing against ASF, but we Hector folk are happy with Github and Google
> groups.

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message