From cassandra-user-return-1277-apmail-incubator-cassandra-user-archive=incubator.apache.org@incubator.apache.org Thu Nov 12 16:43:04 2009 Return-Path: Delivered-To: apmail-incubator-cassandra-user-archive@minotaur.apache.org Received: (qmail 96500 invoked from network); 12 Nov 2009 16:43:03 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 12 Nov 2009 16:43:03 -0000 Received: (qmail 70587 invoked by uid 500); 12 Nov 2009 16:43:03 -0000 Delivered-To: apmail-incubator-cassandra-user-archive@incubator.apache.org Received: (qmail 70571 invoked by uid 500); 12 Nov 2009 16:43:03 -0000 Mailing-List: contact cassandra-user-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: cassandra-user@incubator.apache.org Delivered-To: mailing list cassandra-user@incubator.apache.org Received: (qmail 70562 invoked by uid 99); 12 Nov 2009 16:43:03 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 12 Nov 2009 16:43:03 +0000 X-ASF-Spam-Status: No, hits=2.2 required=10.0 tests=HTML_MESSAGE,SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of jmischo@quagility.com designates 216.154.210.211 as permitted sender) Received: from [216.154.210.211] (HELO quagility.com) (216.154.210.211) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 12 Nov 2009 16:42:54 +0000 Received: from [10.0.69.97] (adsl-69-210-246-66.dsl.chcgil.sbcglobal.net [69.210.246.66]) (authenticated bits=0) by quagility.com (8.13.1/8.13.1) with ESMTP id nACGgWLY029800 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for ; Thu, 12 Nov 2009 10:42:33 -0600 Message-Id: From: Jonathan Mischo To: cassandra-user@incubator.apache.org In-Reply-To: Content-Type: multipart/alternative; boundary=Apple-Mail-86-564077822 Mime-Version: 1.0 (Apple Message framework v936) Subject: Re: Cassandra access control Date: Thu, 12 Nov 2009 10:42:31 -0600 References: <87eio6p7pb.fsf@lifelogs.com> <9c50e66d0911111429n1f23c01ct7a0d3afef3d0a6f6@mail.gmail.com> <13FB79D2-F083-46D0-BD2A-02F915144322@joestump.net> <20091112001409.GC12953@alumni.caltech.edu> <878webssu6.fsf_-_@lifelogs.com> <87iqdfrba9.fsf@lifelogs.com> <5B7ECCB8-BF96-4EA1-AAB7-B8C27B824FDF@quagility.com> X-Mailer: Apple Mail (2.936) X-Virus-Checked: Checked by ClamAV on apache.org --Apple-Mail-86-564077822 Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit On Nov 12, 2009, at 10:38 AM, Jonathan Ellis wrote: > On Thu, Nov 12, 2009 at 10:23 AM, Jonathan Mischo > wrote: >> The problem I see with this is that you can't have a single >> connection >> accessing multiple keyspaces at once. I can think of some cases >> where >> having a single connection access and differentiate between two >> keyspaces >> would be advantageous, especially in certain kinds of reporting >> applications. Otherwise, you force the creation and maintenance of >> multiple >> connection pools on the client side, which isn't as resource >> efficient. > > Let's keep it simple. Forcing multiple connections from a purely > hypothetical use case is a no-brainer tradeoff. Connections are not > expensive. > Even if we can do it sensibly? Connections aren't hugely expensive, but they're not free, either. --Apple-Mail-86-564077822 Content-Type: text/html; charset=US-ASCII Content-Transfer-Encoding: quoted-printable
On Nov 12, 2009, = at 10:38 AM, Jonathan Ellis wrote:

On = Thu, Nov 12, 2009 at 10:23 AM, Jonathan Mischo <jmischo@quagility.com> = wrote:
The problem I see with this is that = you can't have a single connection
accessing multiple keyspaces at once.  I can think of = some cases where
having a = single connection access and differentiate between two = keyspaces
would be = advantageous, especially in certain kinds of = reporting
applications. =  Otherwise, you force the creation and maintenance of = multiple
connection pools on = the client side, which isn't as resource = efficient.

Let's keep it simple.  Forcing = multiple connections from a purely
hypothetical use case is a = no-brainer tradeoff.  Connections are not
expensive.

Even if we can do = it sensibly? Connections aren't hugely expensive, but they're not free, = either.
= --Apple-Mail-86-564077822--