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

Re: I-D Action:draft-snell-http-prefer-03.txt

From: Roy T. Fielding <fielding@gbiv.com>
Date: Tue, 29 Mar 2011 11:46:35 +0200
Cc: Mark Nottingham <mnot@mnot.net>, httpbis mailing list <ietf-http-wg@w3.org>
Message-Id: <BB32FA8E-855D-4155-9715-D7597C5A8438@gbiv.com>
To: "Poul-Henning Kamp" <phk@phk.freebsd.dk>
On Mar 29, 2011, at 11:31 AM, Poul-Henning Kamp wrote:

> In message <B27105DD-AFD1-451C-B9D7-ED79888A657B@mnot.net>, Mark Nottingham wri
> tes:
>>> A URL for this Internet-Draft is:
>>> http://www.ietf.org/internet-drafts/draft-snell-http-prefer-03.txt
> Couldt we please try to make it a habit to include some kind of use-case
> or justification for these "bolt-on" drafts ?
> It's probably my imagination that is flawed, but the only mental connection
> I can attach to this draft is RFC748, so somebody please explain:
> 1. Whats the point.
> 2. How dows this help.
> 3. How much will it help.
> Poul-Henning

heh, I just asked Mark the same question ...

The goal seems to be to ask for the server's result of a PUT or POST
to be returned as part of the same action instead of requiring the
client to make an additional GET request.

The problem with any such desire is that the mechanism handling
a PUT is not always in control of the resource's final state.  The
reason is simply that the mechanism for handling GET may be an
entirely different system from that handling PUT, may have access
to additional sources of metadata, and may be impacted by background
jobs independent of the HTTP request (i.e., event-based triggers on
content changes that result in workflows being run that eventually
change the content shortly after the client has received its response).
Moreover, the programmer writing the PUT handler is probably not
the same programmer developing those other systems, so this feature
is not going to be very reliable.

I agree, the draft should contain use cases to justify the feature
and make it clear that it may only work with very simple,
synchronous, self-contained implementations.

Received on Tuesday, 29 March 2011 09:47:06 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:13:51 UTC