From user-return-13843-apmail-couchdb-user-archive=couchdb.apache.org@couchdb.apache.org Sat Nov 20 03:20:47 2010 Return-Path: Delivered-To: apmail-couchdb-user-archive@www.apache.org Received: (qmail 59002 invoked from network); 20 Nov 2010 03:20:47 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 20 Nov 2010 03:20:47 -0000 Received: (qmail 6224 invoked by uid 500); 20 Nov 2010 03:21:17 -0000 Delivered-To: apmail-couchdb-user-archive@couchdb.apache.org Received: (qmail 5970 invoked by uid 500); 20 Nov 2010 03:21:17 -0000 Mailing-List: contact user-help@couchdb.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@couchdb.apache.org Delivered-To: mailing list user@couchdb.apache.org Received: (qmail 5962 invoked by uid 99); 20 Nov 2010 03:21:16 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 20 Nov 2010 03:21:16 +0000 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests=FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of mikefedyk@gmail.com designates 74.125.82.54 as permitted sender) Received: from [74.125.82.54] (HELO mail-ww0-f54.google.com) (74.125.82.54) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 20 Nov 2010 03:21:09 +0000 Received: by wwi17 with SMTP id 17so3538829wwi.23 for ; Fri, 19 Nov 2010 19:20:48 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:sender:received:date :x-google-sender-auth:message-id:subject:from:to:content-type; bh=ccfuv9Y197g6k6R0YcRZqUwXFVXI0Jc6wuRA6RxJDhU=; b=UzfYgAcQEMoNz0NFrXjoVrWCWqpJ4O597Tc71mqhKfjd86qgJUKboST+sywus3BDVK mAuHol5PLwKX3dZN3ZwtMlLMYjX0WHnWlBp3dWpLnrWgskCojZKjV3s4wnhuoV3lCqLM 4tRTl1K4cKmK5DeGwiyZFON1fB102FUqyWmpk= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:date:x-google-sender-auth:message-id:subject :from:to:content-type; b=XRH/fPIkN7MczEAMjxkat0GvK6dAc8h30S+J8cRwqXPW7GOKce0PLZvcsaLfBD34U9 hC8tvEmQtFr7JdORRBYahrhwBqf0nSLYj/s54t2lok2vgtoWKDAC3CL0v+GXp1MGEGvm zTUwyqXs40TfAJHhpjS+ToxQLr/HwrU0FLYZQ= MIME-Version: 1.0 Received: by 10.216.78.204 with SMTP id g54mr1698764wee.34.1290223247293; Fri, 19 Nov 2010 19:20:47 -0800 (PST) Sender: mikefedyk@gmail.com Received: by 10.216.17.200 with HTTP; Fri, 19 Nov 2010 19:20:47 -0800 (PST) Date: Fri, 19 Nov 2010 19:20:47 -0800 X-Google-Sender-Auth: KxDMJMrxwoxKCHbn8d3TZ1Lllc8 Message-ID: Subject: Best way to monitor _changes when each user/cust is on a separate database? From: Mike Fedyk To: user@couchdb.apache.org Content-Type: text/plain; charset=UTF-8 X-Virus-Checked: Checked by ClamAV on apache.org Hi, I've seen several references to separating users into individual couchdb databases, and I think that may work well for my purposes, but how do I avoid having 1 million sockets long polling on _changes if I have 1 million users/custs/databases? Thanks