Return-Path: Delivered-To: apmail-couchdb-user-archive@www.apache.org Received: (qmail 12727 invoked from network); 8 Apr 2010 02:15:21 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 8 Apr 2010 02:15:21 -0000 Received: (qmail 48827 invoked by uid 500); 8 Apr 2010 02:15:20 -0000 Delivered-To: apmail-couchdb-user-archive@couchdb.apache.org Received: (qmail 48774 invoked by uid 500); 8 Apr 2010 02:15:20 -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 48766 invoked by uid 99); 8 Apr 2010 02:15:20 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 08 Apr 2010 02:15:20 +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 (athena.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; Thu, 08 Apr 2010 02:15:14 +0000 Received: by vws16 with SMTP id 16so81995vws.11 for ; Wed, 07 Apr 2010 19:14:53 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :from:date:received:message-id:subject:to:content-type; bh=muim/cKIfvBzL46ZtR7LVCRKMzuFUj+ihguRsWAE3DI=; b=H/UpjXoiCWPGYsqIeVesM+LR2NLRmEnVhp9gHvpD/MLSkSHFMt2boP7b3B2VnUiLkF hSuoy4bG/Y3jqWgM+he1vQv+YiEhBto//OIqwl50UKOiOnCA9euUdyHNpr9xzYBBngBm MZPoCrjr9N85JIoR0PRdarCADtMXeorgD29eE= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type; b=K4Iqa0iGBVNkJjABh9KQaI4CuTvKvaIt7MvrhqWGckKCPV6G5sornbgGWl6TbXIvD7 wnpprSIYSFOeGBZ3zxJBoGmcJtoRzW7p3G1JDoFPlDz78QgMZ65rPicofyIi18fux7SC d/aN6li4uTv9LJnkUK6tkKo99+2ChXhL0Z0Ho= MIME-Version: 1.0 Received: by 10.220.19.195 with HTTP; Wed, 7 Apr 2010 19:14:33 -0700 (PDT) In-Reply-To: References: From: Ning Tan Date: Wed, 7 Apr 2010 22:14:33 -0400 Received: by 10.220.127.27 with SMTP id e27mr4947578vcs.171.1270692893275; Wed, 07 Apr 2010 19:14:53 -0700 (PDT) Message-ID: Subject: Re: Do change notification (filters) support HTTP verbs other than GET? To: user@couchdb.apache.org Content-Type: text/plain; charset=ISO-8859-1 On Wed, Apr 7, 2010 at 2:05 AM, J Chris Anderson wrote: > > On Apr 6, 2010, at 8:48 AM, Ning Tan wrote: > >> Hello, >> >> Do change notification filters (or change notifications in general) >> support HTTP verbs other than GET? >> > > Currently they only support GET, but it'd be a very short patch to expand support to include POST. Thanks. I'm going to see if I can create such a patch. Time to learn a bit more about Futon tests. Also, in the meantime, I'm trying to "hack" the solution by sending a request body with a GET. It seems that the body reaches my filter function fine (via req.body), but for some reason the response from Couch hangs whenever I send the body, even for a filter function that just returns true. If I remember correctly, the response was like { results: [ and then the curl session just sits there. My curl command was something like: curl -d '["id1","id2"]' -X GET $DB/_changes?filter=app/myFunc The minute I took out the body, the problem went away. I understand that sending a body with GET is not a standard way of doing things, but the hanging part was really weird anyway. It was so close to being a working solution. :-) I can get you more details if needed. Thanks for your help.