From user-return-3653-apmail-couchdb-user-archive=couchdb.apache.org@couchdb.apache.org Sat Feb 21 18:45:42 2009 Return-Path: Delivered-To: apmail-couchdb-user-archive@www.apache.org Received: (qmail 11267 invoked from network); 21 Feb 2009 18:45:42 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 21 Feb 2009 18:45:42 -0000 Received: (qmail 17016 invoked by uid 500); 21 Feb 2009 18:45:40 -0000 Delivered-To: apmail-couchdb-user-archive@couchdb.apache.org Received: (qmail 16984 invoked by uid 500); 21 Feb 2009 18:45:40 -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 16973 invoked by uid 99); 21 Feb 2009 18:45:40 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 21 Feb 2009 10:45:40 -0800 X-ASF-Spam-Status: No, hits=1.5 required=10.0 tests=SPF_PASS,WEIRD_PORT X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of jchris@gmail.com designates 209.85.217.162 as permitted sender) Received: from [209.85.217.162] (HELO mail-gx0-f162.google.com) (209.85.217.162) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 21 Feb 2009 18:45:30 +0000 Received: by gxk6 with SMTP id 6so3790383gxk.11 for ; Sat, 21 Feb 2009 10:45:09 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:received:in-reply-to :references:date:x-google-sender-auth:message-id:subject:from:to :content-type:content-transfer-encoding; bh=6YIMiCh/iL+dDFVxPaNuIVjIABpKx7OaSFWbmK5q5u0=; b=kjJysyMK6J3FbqmUY7s/hTvV/ZYIMo1YQxUIWeRQjNHaPuVeOPv8e5dg56/b7h6byq o+dJrxK09iea2jrGFY+aZM+dS94Che5V65RTUnLssSglaM46xDf5q/gprh4Fcqdbw3ba GXUGMoYmuDL50yet0gkBOpCIHeHz5+PlF4tGs= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type :content-transfer-encoding; b=HDcx74TwOFHUd+D5+BUKK8UbKGmSxD5OwsVHjK6tu8LnbBfRKAzLZWA/KsSAU9wOLd QvpuQZc6MkX+t/C2bJLFm+jUCImCm+b3UeJH8AgSaLo91s9cERSjpJmzb1AW6MyWroXJ gUA0Q89HHGwovZtc/k6rbrun5dKmOKEaKoMCM= MIME-Version: 1.0 Sender: jchris@gmail.com Received: by 10.151.109.11 with SMTP id l11mr1157176ybm.170.1235241909666; Sat, 21 Feb 2009 10:45:09 -0800 (PST) In-Reply-To: <5aaed53f0902211010n2d747276o1ac09d753a9c010@mail.gmail.com> References: <5aaed53f0902210248r18db9382jc0e3b07ef8e48d71@mail.gmail.com> <5aaed53f0902210313x6f4b859bh7670a5fffee3b781@mail.gmail.com> <1BE39A80-CFA6-4D96-914D-E96209CD3834@jasondavies.com> <5aaed53f0902211010n2d747276o1ac09d753a9c010@mail.gmail.com> Date: Sat, 21 Feb 2009 10:45:09 -0800 X-Google-Sender-Auth: 4ea48a9a5923dd75 Message-ID: Subject: Re: [<0.111.0>] Uncaught error in HTTP request: {exit,{body_too_large,content_length}} From: Chris Anderson 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 On Sat, Feb 21, 2009 at 10:10 AM, Jeff Hinrichs - DM&T wrote: > > Google can't seem to help me locate an example of doing a PUT w/ chunked > transfer for httplib2 -- does anyone have any pointers? > Any luck PUTing attachments with chunked encoding? You'll need to create the document first, with a PUT, and then create the attachment, with a chunked PUT. It should be possible to avoid non-buffered non-chunked standalone attachment PUTs now as well, based on my recent patch to Mochiweb. Implementing that would be pretty simple, just a matter of adapting the attachment writing code to handle it. There's not much that can be done about memory usage for inlined base64 attachments. It sounds like that is what you are using for load. In the long run, I'm hoping that a form of the all_docs view can be useful for dump and load. Eg, something like curl http://localhost:5984/olddb/_all_docs?include_everything=true > backup.json followed by curl -X POST -T backup.json http://localhost:5984/newdb/_bulk_docs Would be all that is needed for dump and load. I'm not sure how close we are to this yet, but it sure seems like the simplest way. Chris -- Chris Anderson http://jchris.mfdz.com