Return-Path: Delivered-To: apmail-couchdb-user-archive@www.apache.org Received: (qmail 34922 invoked from network); 26 Jun 2009 08:36:42 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 26 Jun 2009 08:36:42 -0000 Received: (qmail 39296 invoked by uid 500); 26 Jun 2009 08:36:52 -0000 Delivered-To: apmail-couchdb-user-archive@couchdb.apache.org Received: (qmail 39222 invoked by uid 500); 26 Jun 2009 08:36:52 -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 39212 invoked by uid 99); 26 Jun 2009 08:36:52 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 26 Jun 2009 08:36:52 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of oil.crayons@gmail.com designates 74.125.92.24 as permitted sender) Received: from [74.125.92.24] (HELO qw-out-2122.google.com) (74.125.92.24) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 26 Jun 2009 08:36:43 +0000 Received: by qw-out-2122.google.com with SMTP id 3so725666qwe.29 for ; Fri, 26 Jun 2009 01:36:22 -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:message-id:subject:to:content-type :content-transfer-encoding; bh=RVaU4igLjg0T4/hJo51/nHGZsy1bZk2H/qendAXuoEk=; b=Od768dOe70AwDXXF8R/ra2IZKc4ned4UptRLRGNBWBTC+fiHOyiq77S3IsUl1ic7HQ NEv4nEOZOu0qtYoLZ0j7XRCbJqN9YWLXNRT/dUNtkXzi6a3Xwb0b9+X/OSIqkAfdmw0m lggr4lnpsNZ+t5V3iB6vIKVcmDLvKogZm3Jv0= 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:content-transfer-encoding; b=fQAnm6VZz88ntk3AuPxGEgo/pvDBQwD5brPuRUj5HkJN//iM74SwwsSTduDeziAMUE SqtNX9Bdd7Xu6gHN0IJ/5QbWlIiznuS2uCKkw58wwIg8ArpVlpUU0R0eXeEnVIGt1x9x JZEmJ6KvZm2XEKbiOP9XEIgHNkK7EYLr08q7I= MIME-Version: 1.0 Received: by 10.220.76.68 with SMTP id b4mr2925389vck.26.1246005382130; Fri, 26 Jun 2009 01:36:22 -0700 (PDT) In-Reply-To: <20090626082258.222BC2C005D3@bmail01.one.com> References: <20090626075712.BD9C43000204@bmail00.one.com> <2d8fb9950906260107g54ba489dl9f060b3d49fc1d9@mail.gmail.com> <20090626082258.222BC2C005D3@bmail01.one.com> From: Dmitry Unkovsky Date: Fri, 26 Jun 2009 11:36:02 +0300 Message-ID: <558050c20906260136q66b62d73v8cf6a4b699a9b92e@mail.gmail.com> Subject: Re: Re: Extract JSON objects with Python? To: user@couchdb.apache.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org > I want my server application (a pylons server btw) to extract this > information about mark and marcus and present them as JSON objects for > another server to parse in JS. This is why I'm wondering if I can get a > JSON object from the db directly instead of asking for address, phone, > and so on, to build a new JSON object and present. > Why not to query db via _bulk_docs handler from python and then directly send body of db response to your "other" server? You get your json where you need it, so you just can set some mapping to /db/doc_id or /view/key right via some proxy like nginx, or route initial request through python and give back just raw data received from couch.