Return-Path: Delivered-To: apmail-cassandra-user-archive@www.apache.org Received: (qmail 57570 invoked from network); 5 Apr 2010 18:12:38 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 5 Apr 2010 18:12:38 -0000 Received: (qmail 19350 invoked by uid 500); 5 Apr 2010 18:12:37 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 19334 invoked by uid 500); 5 Apr 2010 18:12:37 -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 19326 invoked by uid 99); 5 Apr 2010 18:12:37 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 05 Apr 2010 18:12:37 +0000 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests=FREEMAIL_FROM,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of prescod@gmail.com designates 209.85.160.172 as permitted sender) Received: from [209.85.160.172] (HELO mail-gy0-f172.google.com) (209.85.160.172) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 05 Apr 2010 18:12:31 +0000 Received: by gyh4 with SMTP id 4so2215085gyh.31 for ; Mon, 05 Apr 2010 11:12:10 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:received:in-reply-to :references:from:date:x-google-sender-auth:received:message-id :subject:to:content-type; bh=/8JoZZzXYJRkWS9UPDK4GuAQS2o3IsS/Gef/tuPsfAY=; b=AT5aP8NJhrdGvB4ABIuB/DZhaZqKxnjLakM/Kvm4mn8lamLLwx3HWdU7+HSqf/QXIT 4IReewQQlwSc+eNJu1xtZPL73mcOsTVWEdv+LUmC20s2OtVnVAFGTnUGZCBO98be+INY RqrjP/KovBMMwL3fwC+wSivzjaUtxFnXpAIv0= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:from:date :x-google-sender-auth:message-id:subject:to:content-type; b=UtW2cVs4KGSWPmU42KWv7OPq/aCi3Dyv0AZPDYOjebJngV7xMJAizo6NZtuy6Y0/OL 5u/WiiAz2E83gyCE4fW1m4BFNkmuiw/ruRAoEABFJv3JWU47P546Yz5re/5Nzu6PFO43 JIB+0dUMkSGx7AGgN9amh0yLaGyh+kL+Mzjtk= MIME-Version: 1.0 Sender: prescod@gmail.com Received: by 10.100.231.17 with HTTP; Mon, 5 Apr 2010 11:06:35 -0700 (PDT) In-Reply-To: References: <4BB98AC5.3040607@fourkitchens.com> <4BB99933.6030708@fourkitchens.com> From: Paul Prescod Date: Mon, 5 Apr 2010 11:06:35 -0700 X-Google-Sender-Auth: df27a8f725e93893 Received: by 10.101.202.4 with SMTP id e4mr12677649anq.102.1270491127944; Mon, 05 Apr 2010 11:12:07 -0700 (PDT) Message-ID: Subject: Re: Memcached protocol? To: user@cassandra.apache.org Content-Type: text/plain; charset=UTF-8 X-Virus-Checked: Checked by ClamAV on apache.org On Mon, Apr 5, 2010 at 10:45 AM, Mike Malone wrote: > ... > > FWIW, I added the atomic increment/decrement operations to the Django cache > interface (and wrote that documentation) because the functionality was > useful for large scale apps. I didn't implement atomic increment/decrement > or atomic add for backends that didn't natively support it because, in my > opinion (and in the opinion of the other Django contributors) any site that > requires that sort of functionality should be running memcached as their > cache backend. So I guess what I'm saying is that the functionality _is_ > useful. However, there probably are some users who would find the subset of > the memcache protocol that you _can_ implement on top of Cassandra useful. That's useful information Mike. I am a bit curious about what the most common use cases are for atomic increment/decrement. I'm familiar with atomic add as a sort of locking mechanism. Paul Prescod