Return-Path: Delivered-To: apmail-couchdb-user-archive@www.apache.org Received: (qmail 80871 invoked from network); 29 Apr 2010 05:54:43 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 29 Apr 2010 05:54:43 -0000 Received: (qmail 33467 invoked by uid 500); 29 Apr 2010 05:54:42 -0000 Delivered-To: apmail-couchdb-user-archive@couchdb.apache.org Received: (qmail 33247 invoked by uid 500); 29 Apr 2010 05:54:41 -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 33237 invoked by uid 99); 29 Apr 2010 05:54:41 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 29 Apr 2010 05:54:41 +0000 X-ASF-Spam-Status: No, hits=0.3 required=10.0 tests=AWL,FREEMAIL_FROM,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of jchris@gmail.com designates 74.125.83.52 as permitted sender) Received: from [74.125.83.52] (HELO mail-gw0-f52.google.com) (74.125.83.52) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 29 Apr 2010 05:54:33 +0000 Received: by gwaa18 with SMTP id a18so1560642gwa.11 for ; Wed, 28 Apr 2010 22:54:11 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:content-type:mime-version :subject:from:in-reply-to:date:content-transfer-encoding:message-id :references:to:x-mailer; bh=r+HTZzFXz13z5Aq/sPd7UgUHIaEQSp/DRvzd3gznmxI=; b=jkpZVgME7Lk9KFSPJphMKMwZMTW5xJZBGgK2oz3lHTrc9JsAr4G3EiJZBUGdrz2C48 lDERnLTSKm1EzdFaf5jrJNeJzayfHVwQCgcL6ZmSdDprM9baPA7wICfGf9c39vZ3T/OA okNl3xYd7oPkw98DMouG4yczhMi3SNHtvmDD0= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=content-type:mime-version:subject:from:in-reply-to:date :content-transfer-encoding:message-id:references:to:x-mailer; b=w7FM1mKpLnXY8OnabXKKTdwbE4FmUP+1HEn9a3NeEM4EN+/MGVgexR17G2C+K4z+Ed jROV+5mG3HrFeMkRaUnmCW72le9BcL94vlJ6L/JabMrqQ1upmoc9c2FkVO+kkhnMFZdD kYh/ot7J49E8nd3WWIteksJtH86JXLJdwtTww= Received: by 10.101.79.5 with SMTP id g5mr4030748anl.61.1272520451776; Wed, 28 Apr 2010 22:54:11 -0700 (PDT) Received: from [192.168.1.101] (c-98-248-172-14.hsd1.ca.comcast.net [98.248.172.14]) by mx.google.com with ESMTPS id 20sm518283iwn.13.2010.04.28.22.54.09 (version=TLSv1/SSLv3 cipher=RC4-MD5); Wed, 28 Apr 2010 22:54:10 -0700 (PDT) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Apple Message framework v1078) Subject: Re: adding the ability to do a POST to _changes From: J Chris Anderson In-Reply-To: Date: Wed, 28 Apr 2010 22:54:07 -0700 Content-Transfer-Encoding: quoted-printable Message-Id: References: To: user@couchdb.apache.org X-Mailer: Apple Mail (2.1078) On Apr 28, 2010, at 10:32 PM, Jarrod Roberson wrote: > I have been able to add the ability to do a POST to _changes in > couch_httpd_db.erl but I I just get a raw body element with the string = of > JSON. > How do I get it to parse the json in the body like a keys POST to a = _view? > What I am trying to do is add the ability of a _filter to have a list = of > keys and only send me the ids that are in the list of keys that I = specify in > the POST to _changes. >=20 Your JavaScript function should be able to accept the POST body and use = it to decide whether to return true or false. So you can parse the JSON = in your _filter fun and return true or false based on a docid match. I hope that helps. Thanks for hacking that patch. I owe you some patch application wuffie = b/c I know you have the _list patch for couch.js too. Thanks for the hard work! Cheers, Chris > --=20 > Jarrod Roberson