From dev-return-11996-apmail-couchdb-dev-archive=couchdb.apache.org@couchdb.apache.org Wed Sep 29 12:50:22 2010 Return-Path: Delivered-To: apmail-couchdb-dev-archive@www.apache.org Received: (qmail 53205 invoked from network); 29 Sep 2010 12:50:21 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 29 Sep 2010 12:50:21 -0000 Received: (qmail 99284 invoked by uid 500); 29 Sep 2010 12:50:21 -0000 Delivered-To: apmail-couchdb-dev-archive@couchdb.apache.org Received: (qmail 98890 invoked by uid 500); 29 Sep 2010 12:50: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 98881 invoked by uid 99); 29 Sep 2010 12:50:17 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 29 Sep 2010 12:50:17 +0000 X-ASF-Spam-Status: No, hits=2.2 required=10.0 tests=FREEMAIL_FROM,HTML_MESSAGE,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 jeff.zellner@gmail.com designates 209.85.161.52 as permitted sender) Received: from [209.85.161.52] (HELO mail-fx0-f52.google.com) (209.85.161.52) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 29 Sep 2010 12:50:11 +0000 Received: by fxm17 with SMTP id 17so537282fxm.11 for ; Wed, 29 Sep 2010 05:49:49 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:mime-version:received:from:date :message-id:subject:to:content-type; bh=oTs6gFKodm6jqvN9jcg3X9wR613IQeJXrhkADsC2hWc=; b=tpJTzzLaVmAg6ODzA3oSX2aG1xXFGescnfxJoCLTSgD7Oj/7uY9nQxyYaq2Je7JVo4 F+bCQyw/3oI5gw37onjunw2FH8RivY/7MmFMx3y147rpMtzgA2v6jp3Q/Nw/9cHT6f85 KBS7ZoMeDpFFu8PQ7QWzBTzDfkSzigeqFuUMA= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:from:date:message-id:subject:to:content-type; b=VkJ3mKNcy65NnRcdJi4kJrV07BGQzUwTlNh7212U82HieFjqRgQh0iZ5Q5z02ayZIL X/5SNoBHqPTnwtSp7YapLhn4ZrDcIsbNcMUx2l9IFtLfgeStU8XPtqZUPfy+tJVsHimm thNu5olqfASJkJtWE+7830czUO2Ha2cU6eUaU= Received: by 10.239.148.71 with SMTP id e7mr133202hbb.92.1285764589379; Wed, 29 Sep 2010 05:49:49 -0700 (PDT) MIME-Version: 1.0 Received: by 10.239.184.211 with HTTP; Wed, 29 Sep 2010 05:49:29 -0700 (PDT) From: Jeff Zellner Date: Wed, 29 Sep 2010 08:49:29 -0400 Message-ID: Subject: Multiview handler? To: dev@couchdb.apache.org Content-Type: multipart/alternative; boundary=001485f03dbc9d601b0491656502 --001485f03dbc9d601b0491656502 Content-Type: text/plain; charset=ISO-8859-1 What's the status of a multiview handler? I hear there's one being worked on. Is there anything I can do to help out with it? I wrote one for my immediate use yesterday, but it's pretty ghetto: Used as a httpd_global_handler -- you POST it JSON in the form of { "usersuppliedname1":"view1_query_string", "usersuppliedname2":"view2_query_string", ... etc. } It simply does inets httpc queries and returns the aggregate results in JSON, each keyed by the user supplied name. It works for my purposes (by reducing the number of HTTP requests sent over physical distance), but I'm assuming that the 'real' implementation will query the views through the API, and not through batching remote->local HTTP queries. Cheers! Jeff --001485f03dbc9d601b0491656502--