Mailing-List: contact couchdb-user-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: couchdb-user@incubator.apache.org
Received-SPF: pass (athena.apache.org: local policy)
Date: Tue, 8 Jul 2008 12:22:55 -0600
From: Michael Hendricks <michael@ndrix.org>
To: couchdb-user@incubator.apache.org
Subject: Re: inserting a single document
Message-ID: <20080708182255.GF16398@ginosko.ndrix.org>
References: <20080707220638.GF12208@ginosko.ndrix.org>
 <8E613742-74D7-4F18-917B-D93E845E4CD6@apache.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <8E613742-74D7-4F18-917B-D93E845E4CD6@apache.org>
User-Agent: Mutt/1.5.17 (2007-11-01)

On Tue, Jul 08, 2008 at 12:34:07AM +0200, Jan Lehnardt wrote:
> We strive for buzzword compliance and the buzzword in question
> is REST :-)
>
> Consider a client that is not interested in bulk insertion that only does
> and wants GET/PUT/POST/DELETE to a single resource. That's where
> the singe document PUT/POST API makes sense.

Thanks Jan.  I definitely like the PUT/POST API.  I use it quite a bit
with the couchdb commandline client … curl ;-)  It's sure handy.

> From your library's point of view, only using the bulk API is totally
> acceptable, though.

Great, I'll go ahead and do it that way then.  Thanks.

-- 
Michael