Account Options

  1. Sign in
The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Google Groups Home
« Groups Home
Message from discussion high performance scalable counter

Received: by 10.14.16.161 with SMTP id h33mr171916eeh.47.1312008440308;
        Fri, 29 Jul 2011 23:47:20 -0700 (PDT)
X-BeenThere: google-appengine-go@googlegroups.com
Received: by 10.14.30.217 with SMTP id k65ls882129eea.7.gmail; Fri, 29 Jul
 2011 23:47:19 -0700 (PDT)
Received: by 10.14.187.130 with SMTP id y2mr168714eem.56.1312008439270;
        Fri, 29 Jul 2011 23:47:19 -0700 (PDT)
Received: by 10.14.187.130 with SMTP id y2mr168713eem.56.1312008439256;
        Fri, 29 Jul 2011 23:47:19 -0700 (PDT)
Return-Path: <dsymo...@google.com>
Received: from smtp-out.google.com (hpaq8.eem.corp.google.com [172.25.149.8])
        by gmr-mx.google.com with ESMTPS id i21si4091422eei.0.2011.07.29.23.47.19
        (version=TLSv1/SSLv3 cipher=OTHER);
        Fri, 29 Jul 2011 23:47:19 -0700 (PDT)
Received-SPF: pass (google.com: domain of dsymo...@google.com designates 172.25.149.8 as permitted sender)
Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of dsymo...@google.com designates 172.25.149.8 as permitted sender) smtp.mail=dsymo...@google.com; dkim=pass (test mode) header...@google.com
Received: from hpaq12.eem.corp.google.com (hpaq12.eem.corp.google.com [172.25.149.12])
	by smtp-out.google.com with ESMTP id p6U6lIqv005863
	for <google-appengine-go@googlegroups.com>; Fri, 29 Jul 2011 23:47:18 -0700
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=google.com; s=beta;
	t=1312008439; bh=8cgG2l77l17XjxLwBkvvD2KCUZc=;
	h=MIME-Version:Sender:In-Reply-To:References:Date:Message-ID:
	 Subject:From:To:Content-Type;
	b=D1px6OaMdNHpus45dUaCL1qja0FJuUybM7AOOGoVGLbOzlnn4qtnFIVMBVTCXFkjp
	 FwX/JCw2qMDRnvPd6LMJA==
DomainKey-Signature: a=rsa-sha1; s=beta; d=google.com; c=nofws; q=dns;
	h=dkim-signature:mime-version:sender:in-reply-to:references:date:
	x-google-sender-auth:message-id:subject:from:to:content-type:x-system-of-record;
	b=Gh9JrSWj6YGwjpIgHoVWNYrLKHgjhxKnK27jbHnT/v2bVcjeI36SvEw/JX5P/KaKn
	fNyu3Xum2V2b2vHH6+7uQ==
Received: from qwa26 (qwa26.prod.google.com [10.241.193.26])
	by hpaq12.eem.corp.google.com with ESMTP id p6U6l3OW007351
	(version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=NOT)
	for <google-appengine-go@googlegroups.com>; Fri, 29 Jul 2011 23:47:17 -0700
Received: by qwa26 with SMTP id 26so3065092qwa.14
        for <google-appengine-go@googlegroups.com>; Fri, 29 Jul 2011 23:47:17 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=google.com; s=beta;
        h=mime-version:sender:in-reply-to:references:date
         :x-google-sender-auth:message-id:subject:from:to:content-type;
        bh=NLZnCPnmzOfBY7QBXZxr0E53m6x2L4Zu3K5w161UACQ=;
        b=Ze6I30L8w2ICLAmQQClNx71oJTO1hq7EIsv5BFm0DCuF4QK4AY9udSRQhu1XKX/n2Q
         YD0A47ZVstm1E6/TJ1wQ==
Received: by 10.229.25.69 with SMTP id y5mr1670557qcb.23.1312008437541;
        Fri, 29 Jul 2011 23:47:17 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.229.25.69 with SMTP id y5mr1670552qcb.23.1312008437336; Fri,
 29 Jul 2011 23:47:17 -0700 (PDT)
Sender: dsymo...@google.com
Received: by 10.229.6.205 with HTTP; Fri, 29 Jul 2011 23:47:17 -0700 (PDT)
In-Reply-To: <8168418.4266.1312006898681.JavaMail.geo-discussion-forums@yqim5>
References: <8168418.4266.1312006898681.JavaMail.geo-discussion-forums@yqim5>
Date: Sat, 30 Jul 2011 16:47:17 +1000
Message-ID: <CA+VESTmXS_QBeK9q7E9ZFy8JuOHU=eqmn==0J5_oux2iajg...@mail.gmail.com>
Subject: Re: high performance scalable counter
From: David Symonds <dsymo...@golang.org>
To: google-appengine-go@googlegroups.com
Content-Type: text/plain; charset=ISO-8859-1
X-System-Of-Record: true

On Sat, Jul 30, 2011 at 4:21 PM, Hunka <dev133...@gmail.com> wrote:

> 2. Shared counter - is COOL for example as WEBPAGE Hit Counter,
> but not ideal when there are many objects which can be voted for.

Why isn't that ideal? It sounds like it would be ideal for your use case.


Dave.