- From: Julian Reschke <julian.reschke@gmx.de>
- Date: Fri, 30 Jan 2009 18:01:00 +0100
- To: Cyrus Daboo <cyrus@daboo.name>
- CC: Lisa Dusseault <lisad@messagingarchitects.com>, ietf-http-wg@w3.org
Cyrus Daboo wrote: > ... > Another comment: this draft defines the new 209 status code, yet it does > not clearly explain under what circumstances a server would return the > resulting resource data in the PATCH response. Is that something the > server chooses to do unilaterally, or does the client get to ask the > server to return the result? > > Note that in CalDAV we have the situation now where pretty much every > PUT of a resource has to be followed by a GET because the server is > modifying the resource to account for scheduling actions that happen > synchronously. It would be nice if there were a way for a client to ask > the server to return the (now modified) resource in the PUT response > with a 209 status code. > ... I think what you're looking for is <http://tools.ietf.org/html/draft-snell-http-prefer-00>. This used to be in the PATCH I-D, but James moved it into a separate spec (which I think was a good idea in order to keep PATCH as simple as possible). BR, Julian
Received on Friday, 30 January 2009 17:01:46 UTC