Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id D3CF1200CC5 for ; Tue, 27 Jun 2017 07:42:25 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id D26F3160BDE; Tue, 27 Jun 2017 05:42:25 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 23785160BDA for ; Tue, 27 Jun 2017 07:42:24 +0200 (CEST) Received: (qmail 32864 invoked by uid 500); 27 Jun 2017 05:42:24 -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 32853 invoked by uid 99); 27 Jun 2017 05:42:23 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd4-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 27 Jun 2017 05:42:23 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd4-us-west.apache.org (ASF Mail Server at spamd4-us-west.apache.org) with ESMTP id 29526C061B for ; Tue, 27 Jun 2017 05:42:23 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 0 X-Spam-Level: X-Spam-Status: No, score=0 tagged_above=-999 required=6.31 tests=[HEADER_FROM_DIFFERENT_DOMAINS=0.001, SPF_PASS=-0.001] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new, port 10024) with ESMTP id 6gvfwVvhdHcb for ; Tue, 27 Jun 2017 05:42:20 +0000 (UTC) Received: from smtp.justsomehost.net (smtp.justsomehost.net [204.11.51.157]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTPS id BCB9C5FBBB for ; Tue, 27 Jun 2017 05:42:19 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by smtp.justsomehost.net (Postfix) with ESMTP id CE98D562D7C; Tue, 27 Jun 2017 01:42:13 -0400 (EDT) Received: from smtp.justsomehost.net ([127.0.0.1]) by localhost (smtp.justsomehost.net [127.0.0.1]) (amavisd-new, port 10032) with ESMTP id p8-ZeErkc6wJ; Tue, 27 Jun 2017 01:42:13 -0400 (EDT) Received: from localhost (localhost [127.0.0.1]) by smtp.justsomehost.net (Postfix) with ESMTP id 3EAEE562E5E; Tue, 27 Jun 2017 01:42:13 -0400 (EDT) X-Virus-Scanned: amavisd-new at smtp.justsomehost.net Received: from smtp.justsomehost.net ([127.0.0.1]) by localhost (smtp.justsomehost.net [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id OZCvk6XN3L8j; Tue, 27 Jun 2017 01:42:13 -0400 (EDT) Received: from smtp.justsomehost.net (smtp.justsomehost.net [204.11.51.157]) by smtp.justsomehost.net (Postfix) with ESMTP id 1E5F5562D7C; Tue, 27 Jun 2017 01:42:13 -0400 (EDT) Date: Tue, 27 Jun 2017 01:42:13 -0400 (EDT) From: Joan Touzet Reply-To: Joan Touzet To: Vladimir Kuznetsov Cc: user@couchdb.apache.org Message-ID: <108567400.1449.1498542131968.JavaMail.Joan@RITA> In-Reply-To: <71E5C0C4-27A8-4DED-BB53-8CA6CCAA4383@gmail.com> References: <5B8E4FB0-A875-4F16-9FB7-8775DD95FA73@gmail.com> <1952339179.1395.1498537282310.JavaMail.Joan@RITA> <71E5C0C4-27A8-4DED-BB53-8CA6CCAA4383@gmail.com> Subject: Re: _global_changes purpose MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Originating-IP: [204.11.51.157] X-Mailer: Zimbra 8.6.0_GA_1194 (Zimbra Desktop/7.3.0_13060_Windows) Thread-Topic: _global_changes purpose Thread-Index: XGSC36Yt/UN3Aby1TBsUOg6MLNvi1Q== archived-at: Tue, 27 Jun 2017 05:42:26 -0000 _db_updates is powered by the _global_changes database. -Joan ----- Original Message ----- From: "Vladimir Kuznetsov" To: user@couchdb.apache.org, "Joan Touzet" Sent: Tuesday, 27 June, 2017 12:39:55 AM Subject: Re: _global_changes purpose Hi Joan I heard /_db_updates is the feed-like thing I could subscribe to listen to the global updates(same way you described). It is not very clear why would I need access to _global_changes database when I already have /_db_updates method with pagination and long-polling features. Is listening on _global_changes's /_changes feed the same as listening on /_db_updates? Or is there any difference? What is preferred? thanks, --Vovan > On Jun 26, 2017, at 9:21 PM, Joan Touzet wrote: > > Say you have 100 databases and you want to know when something changes on all > of them. In 1.x you have to open 100 _changes continuous feeds to get that > information. In 2.x you have to open a single connection to _global_changes. > > Think of the possibilities. > > -Joan > > ----- Original Message ----- > From: "Vladimir Kuznetsov" > To: user@couchdb.apache.org > Sent: Monday, 26 June, 2017 8:47:46 PM > Subject: _global_changes purpose > > Hi guys > > I cannot find any good explanation what's the purpose of _global_changes system database in CouchDB 2.0. Can somebody please explain or provide some pointer? > > thanks > --Vovan