Return-Path: Delivered-To: apmail-cassandra-user-archive@www.apache.org Received: (qmail 47031 invoked from network); 10 Aug 2010 12:00:27 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 10 Aug 2010 12:00:27 -0000 Received: (qmail 5721 invoked by uid 500); 10 Aug 2010 12:00:25 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 5531 invoked by uid 500); 10 Aug 2010 12:00:21 -0000 Mailing-List: contact user-help@cassandra.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@cassandra.apache.org Delivered-To: mailing list user@cassandra.apache.org Received: (qmail 5513 invoked by uid 99); 10 Aug 2010 12:00:19 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 10 Aug 2010 12:00:19 +0000 X-ASF-Spam-Status: No, hits=2.9 required=10.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_NONE,SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (athena.apache.org: local policy) Received: from [209.85.161.172] (HELO mail-gx0-f172.google.com) (209.85.161.172) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 10 Aug 2010 12:00:12 +0000 Received: by gxk20 with SMTP id 20so2304736gxk.31 for ; Tue, 10 Aug 2010 04:59:51 -0700 (PDT) MIME-Version: 1.0 Received: by 10.150.31.13 with SMTP id e13mr19715656ybe.302.1281441591338; Tue, 10 Aug 2010 04:59:51 -0700 (PDT) Received: by 10.220.185.4 with HTTP; Tue, 10 Aug 2010 04:59:50 -0700 (PDT) In-Reply-To: References: <1939FBE7-4DD1-4591-A1A5-24BF53848ACF@thelastpickle.com> Date: Tue, 10 Aug 2010 07:59:50 -0400 Message-ID: Subject: Re: non blocking Cassandra with Tornado From: Ryan Daum To: user@cassandra.apache.org Content-Type: multipart/alternative; boundary=000e0cd35788da2709048d76de4b --000e0cd35788da2709048d76de4b Content-Type: text/plain; charset=ISO-8859-1 > > >> Barring this we (place where I work, Chango) will probably eventually fork >> Cassandra to have a RESTful interface and use the Jetty async HTTP client to >> connect to it. It's just ridiculous for us to have threads and associated >> resources tied up on I/O-blocked operations. >> > > We've done exactly this but with Netty rather than Jetty. Helps too because > we can easily have testers look at what we put into our CFs. Took some > cheating to marshall the raw binaries into JSON but I'm pretty happy with > what it's bought us so far. > Are you capable/willing/interested in sharing the work you did? Ryan --000e0cd35788da2709048d76de4b Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable

Barring this we (place where I work, Chango) will proba= bly eventually fork Cassandra to have a RESTful interface and use the Jetty= async HTTP client to connect to it. It's just ridiculous for us to hav= e threads and associated resources tied up on I/O-blocked operations.

We've done exactly this but with= Netty rather than Jetty. Helps too because we can easily have testers look= at what we put into our CFs. Took some cheating to marshall the raw binari= es into JSON but I'm pretty happy with what it's bought us so far.= =A0

Are you capable/willing/interested in sharing t= he work you did?=A0

Ryan
--000e0cd35788da2709048d76de4b--