Mailing-List: contact dev-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@couchdb.apache.org
Received-SPF: pass (nike.apache.org: domain of jared3d@gmail.com designates
 74.125.44.30 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:from:date:message-id:subject:to
         :cc:content-type:content-transfer-encoding;
        b=PwnwD8bn/VPjy3Izko7lPfv4Vf6wbql4w634hL8jXa67LvT4iCFCyNoeMxaxjVbm6r
         NFsbxGpiE2+JpUjg0yJBfFLtfTZRRFq/x9cUHFAr4BFIJeaEyHVF+E9LJ9CPpAcmEF1R
         KSMcEELquL9xOOs88qovwloV/3XgPwbXx35Yw=
MIME-Version: 1.0
In-Reply-To: <20090514132910.GA12800@uk.tiscali.com>
References: <94efd83c0905140445t615c6982h9bb6cfc923801e12@mail.gmail.com>
	<20090514115501.GA10619@uk.tiscali.com>
 <94efd83c0905140508s5578bafbo3f78082e474c3fae@mail.gmail.com>
	<20090514132910.GA12800@uk.tiscali.com>
From: Jared Scheel <jared3d@gmail.com>
Date: Thu, 14 May 2009 09:04:11 -0500
Message-ID: <94efd83c0905140704g8bf00efh29e6df790a9151ae@mail.gmail.com>
Subject: Re: Allow overridden request methods
To: Brian Candler <B.Candler@pobox.com>
Cc: dev@couchdb.apache.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

True, true. It would definitely get around that.

-Jared

On Thu, May 14, 2009 at 8:29 AM, Brian Candler <B.Candler@pobox.com> wrote:
> On Thu, May 14, 2009 at 07:08:21AM -0500, Jared Scheel wrote:
>> Hmm, didn't think about that. I guess you will need to have some kind
>> of request body anyways. Do you think that the request method should
>> be set in the data though, or should it be set in the header, since
>> the method/header defines how the data should be interpreted? I know
>> that's just splitting hairs, but there was some concern about keeping
>> the api as clean as possible.
>
> I think the whole point is to support minimal HTTP clients. If they don't
> support PUT or DELETE, there's a good chance they don't support custom HTTP
> headers either.
>