Mailing-List: contact dev-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@couchdb.apache.org
Received-SPF: pass (athena.apache.org: domain of bchesneau@gmail.com
 designates 72.14.220.159 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:date:message-id:subject:from:to:content-type;
        b=a2Uy7Z5gA9XP+1QpSfu6NdsUmGpIVNbw9UUd4rbFCo6TRkI05sMNG2eHZAdibIGLS2
         utCdKmYTcgig/FxBLFDQpLmwSlWXjA32j1WDPkbEXL6G9NqPxFtT02qMtLdxmV1KaGis
         REZmwhNRSpOYDYfSr10/BfKvPRR7vQ2gOlwEo=
MIME-Version: 1.0
Date: Sun, 13 Sep 2009 10:00:14 +0200
Message-ID: <b7cd8ed10909130100ie462c8cpe6baac3ceb42dff4@mail.gmail.com>
Subject: POST/PUT on _show vs POST/PUT on _update + GET on _show
From: Benoit Chesneau <bchesneau@gmail.com>
To: dev@couchdb.apache.org
Content-Type: text/plain; charset=ISO-8859-1

Following our discussion with jan____ and jchris on irc i'm asking
here my question if having POST/PUT on _show wouldn't be enough rather
than having a special handler for this. Main raison about it, would be
that it would me more restful. Imho it also offers a simple API on
client side.

jan__ args that it would mess the api. And indeed if you accept
POST/PUT you need to say to couchdb what you return (doc, http
response, newdoc ...). I guess defaults could be POST = new doc, PUT =
update doc like current api on /db/docid, maybe ther is a smart way to
handle it. I was thinking to something like sammyjs, with get/post/put
response and filter on Accept format which is now handle by
respondWith.

What do you think about it ? The proper point is to replace or skip
the need of another handler and make it more simple/restful.

- benoit