- From: Greg Stein <gstein@lyra.org>
- Date: Wed, 20 Dec 2000 13:59:55 -0800
- To: ietf-dav-versioning@w3.org
On Wed, Dec 20, 2000 at 01:43:24PM -0800, Greg Stein wrote: >... > i. Subversion-specific items: a custom report, DAV:version-name > must be an integer representing repository-global-change, atomic > CHECKIN of activities, DAV:prop supported within the DAV:checkin > element (to enable returning post-checkin information, such as > new version resource URLs), possibly other TBD items??? Note the bit in there about DAV:prop in the CHECKIN of an activity. It would be great if that could be formalized, along with a response body for the CHECKIN. The motivation is pretty simple: the CHECKIN can construct a *bunch* of new version resources. It would be nice to have the CHECKIN return that information to you (since it already has it), then for the client to go crawling back over the server fetching all that data. The interesting question, of course, is what resource the DAV:prop applies to. Is it the version selector? No, because those aren't involved in the checkout or checkin (we originally checked out version resources). So it is most likely going to refer to the new version resource. I'm fine with that, as I can get the DAV:version, DAV:getetag, and DAV:version-name properties from that and be okay. But depending on what you CHECKIN, I could see the DAV:prop potentially applying to different items. IMO, it would always apply to the newly-created version resource(s). Cheers, -g -- Greg Stein, http://www.lyra.org/
Received on Wednesday, 20 December 2000 16:56:13 UTC