W3C home > Mailing lists > Public > ietf-http-wg@w3.org > January to March 2012

Re: HTTP at a glance

From: Amos Jeffries <squid3@treenet.co.nz>
Date: Wed, 29 Feb 2012 11:16:55 +1300
To: Martin Thomson <martin.thomson@gmail.com>
Cc: "Roy T. Fielding" <fielding@gbiv.com>, <ietf-http-wg@w3.org>
Message-ID: <29e829a75da6a761cd2c2f8af7c45a96@treenet.co.nz>
On 29.02.2012 07:31, Martin Thomson wrote:
> On 27 February 2012 13:23, Roy T. Fielding <fielding@gbiv.com> wrote:
>> No, POST can create resources.  The only difference is that the 
>> client doesn't
>> know how the resource(s) will be identified after being created.
>
> And some of us really like having some control over our own URI 
> space,
> preferring this approach over PUT.  I wouldn't characterize that as a
> mistake, just a choice.


The blessed way to do that is with a 3xx redirect instructing the 
client where you want the resource PUT if they somehow get it wrong. (Or 
just plain denying wrong PUT if you dont want third-party scripts using 
PUT on your site.)


Yes, I too see a bandwidth problem with that blessed way of doing 
things. Perhapse what is needed is a response indicating "okay, but 
change the URI to X" which does not involve a repeated PUT action. The 
plain PUT+200 sequence seems not to do that easily (workable ideas 
welcome. With my web-dev hat on I have an interest in implementing).

AYJ
Received on Tuesday, 28 February 2012 22:17:22 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 27 April 2012 06:51:56 GMT