- From: Lisa Dusseault <lisa@osafoundation.org>
- Date: Wed, 30 Jul 2008 10:35:07 +0100
- To: Julian Reschke <julian.reschke@gmx.de>
- Cc: WebDAV <w3c-dist-auth@w3.org>
I like this Lisa On Jul 30, 2008, at 10:22 AM, Julian Reschke wrote: > > Hi, > > I proposed an ADDMEMBER method some time ago (<http://greenbytes.de/tech/webdav/draft-reschke-http-addmember-00.html > >), and one feedback I got was that it's not needed because it > duplicates POST. > > In fact, Atompub (RFC 5023) uses POST exactly this way. > > My main concern with this approach is that clients in general do not > know what the semantics of a POST will be, so the servers needs to > tell them in some way. In HTML forms are used, in Atompub it's part > of the contract for collections. > > So how about something like this: > > - define a new live property on collections, "post-location", > containing an DAV:href element identifying a resource that the > client can POST to > > - servers that already use POST on collections would just assign a > different URI for that service, others could just use the > collection's URI > > - POST would work as in AtomPub: post any type of content, server > stores it, and returns new URI in Location header. > > - we probably would also want to include the Slug header, as defined > in <http://greenbytes.de/tech/webdav/rfc5023.html#rfc.section.9.7>. > > (I recall people were unhappy with CalDAV requiring support for PUT, > could this be useful over there as well?) > > BR, Julian >
Received on Wednesday, 30 July 2008 09:50:23 UTC