From user-return-22401-apmail-couchdb-user-archive=couchdb.apache.org@couchdb.apache.org Sun Oct 7 07:56:41 2012 Return-Path: X-Original-To: apmail-couchdb-user-archive@www.apache.org Delivered-To: apmail-couchdb-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 53AF7D2B4 for ; Sun, 7 Oct 2012 07:56:41 +0000 (UTC) Received: (qmail 94940 invoked by uid 500); 7 Oct 2012 07:56:39 -0000 Delivered-To: apmail-couchdb-user-archive@couchdb.apache.org Received: (qmail 94909 invoked by uid 500); 7 Oct 2012 07:56:39 -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 94901 invoked by uid 99); 7 Oct 2012 07:56:39 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 07 Oct 2012 07:56:39 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: local policy) Received: from [91.195.24.3] (HELO mail.open.bg) (91.195.24.3) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 07 Oct 2012 07:56:34 +0000 Received: from [78.83.22.128] (port=54495 helo=localhost.localdomain) by mail.open.bg with esmtpsa (Cipher SSL3.0:DHE_RSA_AES_128_CBC_SHA1:16) (Exim 4.77) id 1TKlie-0002L6-GR by authid with login for ; Sun, 07 Oct 2012 10:56:12 +0300 Date: Sun, 7 Oct 2012 10:56:11 +0300 From: svilen To: user@couchdb.apache.org Subject: Re: can i listen to changes of whole server, not per-db? Message-ID: <20121007105611.2eebd343@svilendobrev.com> In-Reply-To: References: <20121007085933.472ff68a@svilendobrev.com> X-Mailer: Claws Mail 3.8.1 (GTK+ 2.24.13; i686-pc-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org what i am trying to do is similar to syncpoint. effectively couchdb is the api-message-carrier. The idea of database-as-security-domain also fits perfectly - users would see/replicate only dbs that they belong to. But - N users working in M databases means listening to N+M changes-feeds and post-processing them. lumping all in one db, and filtering that into internally-filtered partial replications (a filter per user) seems ... rather tricky. can a client-replicator talk to http-proxy that looks like normal couchdb but is (invisibly-to-client) routed into a filtered-replication? ah i should think how these can scale too.. svil On Sun, 7 Oct 2012 09:27:18 +0200 Dave Cottlehuber wrote: > On 7 October 2012 07:59, svilen wrote: > > g'day > > > > i'm going to have thousands of databases. They are all of similar > > kind, but belong to different (groups of) users, so can't be > > bundled into one. And setupping 10000 connections to > > couchdb/dbXXXXX/_changes doesn't seem very neat, even if on same > > machine. > > Not possible today unfortunately. > > Has anybody got any numbers or experience on practical limits of > _changes feeds connections to a single server? > > A+ > Dave