From couchdb-user-return-224-apmail-incubator-couchdb-user-archive=incubator.apache.org@incubator.apache.org Mon Apr 14 20:37:01 2008 Return-Path: Delivered-To: apmail-incubator-couchdb-user-archive@locus.apache.org Received: (qmail 1556 invoked from network); 14 Apr 2008 20:37:01 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 14 Apr 2008 20:37:01 -0000 Received: (qmail 19717 invoked by uid 500); 14 Apr 2008 20:37:01 -0000 Delivered-To: apmail-incubator-couchdb-user-archive@incubator.apache.org Received: (qmail 19686 invoked by uid 500); 14 Apr 2008 20:37:01 -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 19677 invoked by uid 99); 14 Apr 2008 20:37:01 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 14 Apr 2008 13:37:01 -0700 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of jchris@gmail.com designates 72.14.220.154 as permitted sender) Received: from [72.14.220.154] (HELO fg-out-1718.google.com) (72.14.220.154) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 14 Apr 2008 20:36:16 +0000 Received: by fg-out-1718.google.com with SMTP id 22so1718590fge.26 for ; Mon, 14 Apr 2008 13:36:27 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:sender:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth; bh=dz+MFkbpNkOrm+tqzFEuBVbTwsF4DDSLzFDZYXt9ff4=; b=XO7Wox7FAXTtjty3CTXhnEwP4xyAvWNERsW4MXcqYdDY7aQE8akXDi6el2KpQI8sqFgn5vs5IURBgk99tjgrWKwnZHlLWKcIraX4sG1Rr9EIcDZZVSt8nJz4oF8ah5xUpi/1z1KvM7DJhVB/pxS05H9X3TPqCb/5iQZc8IZrU/s= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:sender:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth; b=Spb0ivDCpJrvos/3IeF0P5CElw22SOUaF+tlf9D/6L3dCRQDReBxwoSrjdnOK3Y9ScJvx7K4SvWiEHoG/CQGvUndZHAMAztExQnofmqbCX2edL3QeZRwU99qsX6Ar0HMlq54kVNyQmgrbOGHJnT5ZbSSTb7FptHeTjCUqrPBZd0= Received: by 10.86.66.19 with SMTP id o19mr14244154fga.46.1208205387860; Mon, 14 Apr 2008 13:36:27 -0700 (PDT) Received: by 10.86.57.13 with HTTP; Mon, 14 Apr 2008 13:36:27 -0700 (PDT) Message-ID: Date: Mon, 14 Apr 2008 13:36:27 -0700 From: "Chris Anderson" Sender: jchris@gmail.com To: couchdb-user@incubator.apache.org Subject: Re: PUT / POST tradeoffs In-Reply-To: <001401c89e6d$f016d070$0302a8c0@T60> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <001401c89e6d$f016d070$0302a8c0@T60> X-Google-Sender-Auth: a26451565d4e2c8d X-Virus-Checked: Checked by ClamAV on apache.org On Mon, Apr 14, 2008 at 1:27 PM, Brian Smith wrote: > > PUT is almost always better than POST; if you experience network > failures, you can retry the PUT without any ill effects. If you use > POST, and your experience a network partition before you get the > response, how will you determine whether or not the POST succeeded? See > "Post Once Exactly" (http://www.mnot.net/blog/2005/03/21/poe), HTTPLR > (http://dehora.net/doc/httplr/draft-httplr-01.html), and their related > discussions. Thanks Brian - I think I meant PUT... I've been using the batch POST (which acts like PUT if you specify the document_id) so I spoke a little fuzzily. And that's an extremely clear rational for PUT. Chris -- Chris Anderson http://jchris.mfdz.com