From user-return-9797-apmail-couchdb-user-archive=couchdb.apache.org@couchdb.apache.org Tue Apr 06 15:49:01 2010 Return-Path: Delivered-To: apmail-couchdb-user-archive@www.apache.org Received: (qmail 48592 invoked from network); 6 Apr 2010 15:49:01 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 6 Apr 2010 15:49:01 -0000 Received: (qmail 81481 invoked by uid 500); 6 Apr 2010 15:49:00 -0000 Delivered-To: apmail-couchdb-user-archive@couchdb.apache.org Received: (qmail 81369 invoked by uid 500); 6 Apr 2010 15:48:59 -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 81361 invoked by uid 99); 6 Apr 2010 15:48:59 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 06 Apr 2010 15:48:59 +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 ningtan@gmail.com designates 209.85.212.52 as permitted sender) Received: from [209.85.212.52] (HELO mail-vw0-f52.google.com) (209.85.212.52) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 06 Apr 2010 15:48:52 +0000 Received: by vws3 with SMTP id 3so5515vws.11 for ; Tue, 06 Apr 2010 08:48:31 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:from:date:received :message-id:subject:to:content-type; bh=kJ4qe8Cug5HegaebiwvwwqC5QK8XmaKSG1A6t3FsEb8=; b=qbJZQCbZ4RbMMmuNZQsFNRg/pr35OwhPI7lUJHL9VuKlVSidwhZdUdfPtmdTV7QizH fNQhmcHoT2RHF7UTh4nSgNkxPBbxTmOnoChjEC5Z/FmEBq9dtUhT1AKGyfT85mjz4ob2 /uIp2JQqqdvbNLe5r1Ozc/RGJovlFAchrSgQA= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:from:date:message-id:subject:to:content-type; b=FXZkS9HKRZrdEEJUlHy65YQ7NiqWajiQgRw3mnVrGe7AyE6CuHn/HMJsO3U99P9CJX zZHKB61A+XDFlBpMrRfx87rEYGdhnNzxpiNfbtGWEEUcjSfZfydMrgx1smK7cDBVivWv ZgDPVr1yrdorxVK8ZgrCMQz9IEkA4OMw21RX4= MIME-Version: 1.0 Received: by 10.220.19.195 with HTTP; Tue, 6 Apr 2010 08:48:11 -0700 (PDT) From: Ning Tan Date: Tue, 6 Apr 2010 11:48:11 -0400 Received: by 10.220.61.201 with SMTP id u9mr3523074vch.40.1270568911101; Tue, 06 Apr 2010 08:48:31 -0700 (PDT) Message-ID: Subject: Do change notification (filters) support HTTP verbs other than GET? To: user@couchdb.apache.org Content-Type: text/plain; charset=ISO-8859-1 X-Virus-Checked: Checked by ClamAV on apache.org Hello, Do change notification filters (or change notifications in general) support HTTP verbs other than GET? We are implementing a notification filter that accepts a number of doc IDs (passed in by the client) and only select changes in that set. The client decides which doc IDs it's interested in. I'm worried about the query string length limitation. Is this a valid concern? Does there exist some better way to handle what we need done? Thanks.