W3C home > Mailing lists > Public > ietf-http-wg@w3.org > July to September 2006

Re: I-D ACTION:draft-reschke-http-etag-on-write-00.txt

From: Cyrus Daboo <cyrus@daboo.name>
Date: Wed, 09 Aug 2006 16:12:08 -0700
To: sh@defuze.org, Julian Reschke <julian.reschke@gmx.de>
cc: HTTP Working Group <ietf-http-wg@w3.org>
Message-ID: <3BB9635DBD77C90F1B8D47B9@wwdc-77-126.apple.com>

Hi Sylvain,

--On August 9, 2006 10:35:28 PM +0100 Sylvain Hellegouarch <sh@defuze.org> 
wrote:

> I'm not sure the Entity-Transform header is needed since you might as
> well achieve the same result by using both the status code and the
> content type of the returned entity.
>
> Server does not modify the resource => Sends a 204 No Content
> Server does modify the resource => Sends a 200 and the newly created
> entity with its new media-type.
>
> That way the user agent knows if the resource has been modified and how.

Not all clients will want to get the updated resource back from the server, 
so having the server always return it is not ideal, and in some 
environments (mobile devices) extremely bad!

-- 
Cyrus Daboo
Received on Wednesday, 9 August 2006 23:15:09 GMT

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