Return-Path: Delivered-To: apmail-incubator-couchdb-user-archive@locus.apache.org Received: (qmail 77419 invoked from network); 12 Nov 2008 20:33:31 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 12 Nov 2008 20:33:31 -0000 Received: (qmail 13750 invoked by uid 500); 12 Nov 2008 20:33:37 -0000 Delivered-To: apmail-incubator-couchdb-user-archive@incubator.apache.org Received: (qmail 13716 invoked by uid 500); 12 Nov 2008 20:33:37 -0000 Mailing-List: contact couchdb-user-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: couchdb-user@incubator.apache.org Delivered-To: mailing list couchdb-user@incubator.apache.org Received: (qmail 13704 invoked by uid 99); 12 Nov 2008 20:33:37 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 12 Nov 2008 12:33:37 -0800 X-ASF-Spam-Status: No, hits=3.2 required=10.0 tests=HTML_MESSAGE,SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (athena.apache.org: local policy) Received: from [209.85.162.179] (HELO el-out-1112.google.com) (209.85.162.179) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 12 Nov 2008 20:32:18 +0000 Received: by el-out-1112.google.com with SMTP id y26so406392ele.18 for ; Wed, 12 Nov 2008 12:33:01 -0800 (PST) Received: by 10.90.67.10 with SMTP id p10mr2541039aga.71.1226521981001; Wed, 12 Nov 2008 12:33:01 -0800 (PST) Received: by 10.90.90.17 with HTTP; Wed, 12 Nov 2008 12:33:00 -0800 (PST) Message-ID: <64a10fff0811121233v57f640d3x9b7f02bf5b0121b7@mail.gmail.com> Date: Wed, 12 Nov 2008 15:33:00 -0500 From: "Dean Landolt" To: couchdb-user@incubator.apache.org Subject: Re: Seeking advice on using couchdb for rewritting a project. In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_17057_12791625.1226521981002" References: <4919C8A7.8030409@gmail.com> <2966DD15-EBB2-47E8-8F17-6A74888B7829@gmail.com> <64a10fff0811121126o22fe1bcbtadd09f1252fd24a@mail.gmail.com> <366621.99080.qm@web57201.mail.re3.yahoo.com> X-Virus-Checked: Checked by ClamAV on apache.org ------=_Part_17057_12791625.1226521981002 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline On Wed, Nov 12, 2008 at 3:26 PM, Chris Anderson wrote: > I believe this is the relevant spec: > > http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html#sec14.35 > > Range requests seems like an edge case, and then you turn out to need > them. I'd advocate that we only provide this functionality for > attachments. Making it work for regular JSON requests seems like pure > folly. Certainly. That seems like a pretty reasonable spec though, and now that I think about it, it should be up to the client to handle any interpretation of indexes to get the relevant range. I'll open up a JIRA. ------=_Part_17057_12791625.1226521981002--