Cyrus Daboo wrote: > ... > With PUT, there is already a body being sent - i.e. the actual data of > the resource. So there is no place to put the extension data, except for > the request header (which would not be ideal). One solution, of course, > would be to use a special MIME body with PUT, e.g. a multipart/mixed > where the first part is application/webdav+properties, and the second > part is the actual resource body data. Not sure what implication that > might have. > ... With PUT we would need a way to make sure that the recipient does understand the new MIME type we defined. Instead of overloading PUT, using a body+metadata MIME type with PATCH might work better. Best regards, JulianReceived on Monday, 19 November 2007 13:02:19 GMT
This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 19 November 2007 13:02:20 GMT