Return-Path: X-Original-To: apmail-couchdb-dev-archive@www.apache.org Delivered-To: apmail-couchdb-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 190E5F129 for ; Sun, 7 Apr 2013 09:07:19 +0000 (UTC) Received: (qmail 76168 invoked by uid 500); 7 Apr 2013 09:07:18 -0000 Delivered-To: apmail-couchdb-dev-archive@couchdb.apache.org Received: (qmail 76089 invoked by uid 500); 7 Apr 2013 09:07:18 -0000 Mailing-List: contact dev-help@couchdb.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@couchdb.apache.org Delivered-To: mailing list dev@couchdb.apache.org Received: (qmail 76037 invoked by uid 99); 7 Apr 2013 09:07:16 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 07 Apr 2013 09:07:16 +0000 Date: Sun, 7 Apr 2013 09:07:15 +0000 (UTC) From: "Idan Zalzberg (JIRA)" To: dev@couchdb.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (COUCHDB-1763) Notification changes timeout is reset on filtered changes MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/COUCHDB-1763?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Idan Zalzberg updated COUCHDB-1763: ----------------------------------- Component/s: (was: Database Core) HTTP Interface > Notification changes timeout is reset on filtered changes > --------------------------------------------------------- > > Key: COUCHDB-1763 > URL: https://issues.apache.org/jira/browse/COUCHDB-1763 > Project: CouchDB > Issue Type: Bug > Components: HTTP Interface > Reporter: Idan Zalzberg > > using _changes api with longpoll feed, and the 'timeout' parameter > I also have a custom filter method that checks if the changes are relevant. > When a change comes in that returns False on the filter method, the long polling does not return (as it should), but the timeout is reset. > For example. > if I call the _changes api with timeout 10 on time 0 it will return at time 10 if no changes occurred (as it should). > However, if a change comes in at the time 5 that doesn't pass the filter method, the changes api will only return at time 15, leading me to believe that even though the change fell through the filter, the 10 sec timeout was somehow reset and started from 0 again. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira