Mailing-List: contact cassandra-user-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: cassandra-user@incubator.apache.org
Received-SPF: neutral (nike.apache.org: local policy)
Subject: Re: finding Cassandra servers
From: Eric Evans <eevans@rackspace.com>
To: cassandra-user@incubator.apache.org
In-Reply-To: <87fx4hpezm.fsf@lifelogs.com>
References: <87hbozq574.fsf@lifelogs.com> <87eik1lf8b.fsf@lifelogs.com>
	 <1c6fcff1003030557v527c2dcbn78e1ea9f93adc328@mail.gmail.com>
	 <87k4ttqy8k.fsf@lifelogs.com>
	 <1c6fcff1003030641g4737155fl4cb9b901bd9ebf13@mail.gmail.com>
	 <87zl2pphvd.fsf@lifelogs.com>
	 <1c6fcff1003030732i5b17be81g38629aaaaa3eecb@mail.gmail.com>
	 <87fx4hpezm.fsf@lifelogs.com>
Content-Type: text/plain; charset="UTF-8"
Date: Wed, 03 Mar 2010 10:43:19 -0600
Message-ID: <1267634599.17434.30.camel@erebus.lan>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit

On Wed, 2010-03-03 at 10:05 -0600, Ted Zlatanov wrote:
> I can do a patch+ticket for this in the core, making it optional and
> off by default, or do the same for a contrib/ service as you
> suggested.  So I'd appreciate a +1/-1 quick vote on whether this can
> go in the core to save me from rewriting the patch later.

I don't think voting is going to help. Voting doesn't do anything to
develop consensus and it seems pretty clear that no consensus exists
here.

It's entirely possible that you've identified a problem that others
can't see, or haven't yet encountered. I don't see it, but then maybe
I'm just thick.

Either way, if you think this is important, the onus is on you to
demonstrate the merit of your idea and contrib/ or a github project is
one way to do that (the latter has the advantage of not needing to rely
on anyone else).


-- 
Eric Evans
eevans@rackspace.com