couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Noah Slater <nsla...@apache.org>
Subject Re: Using HTTP headers
Date Thu, 19 Feb 2009 23:42:34 GMT
On Thu, Feb 19, 2009 at 03:27:26PM -0800, Chris Anderson wrote:
> On Thu, Feb 19, 2009 at 3:19 PM, Chris Anderson <jchris@apache.org> wrote:
> > ... it doesn't quite fit in the resource identifier
> > either.
>
> When you:
>
> PUT /db/docid?rev=R
>
> vs
>
> PUT /db/docid?rev=R&full_commit=true
>
> They are the same resource (so these URLs are misleading). But I kinda
> think full-commit should go in the URI anyway, just so that weak
> clients can use it.

But are they the same resource? Is it not up to the server to decide what
resource to create, and how to create it, depending on the URI the client uses
to PUT the representation?

I suspect that using query strings with PUT methods like this is RESTful.

-- 
Noah Slater, http://tumbolia.org/nslater

Mime
View raw message