UUIDs during updates

Part of mbk's original UUID change was to have mod_dav_svn marshall
UUIDs as live "entry props" in an update report.

This ended up choking most clients, which have overly-strict xml
validation (now fixed in 0.19)... but nonetheless, we #if 0'd out this
feature in the 0.19 release branch for compatibility courtesy.

At the moment, mod_dav_svn in /trunk *is* sending UUID properties in
an update response. After some discussion in the Chicago office, we'd
like to advocate that we remove this feature from /trunk as well,
permanently.

In a nutshell: there's no point in sending UUIDs this way. The other
update-report 'entry' props are dynamic things; if the update report
says a file has changed, then by gum, the created-rev, author, and
date have probably changed as well. But the UUID is invariant.

Furthermore, the UUID live-property still exists on every resource.
That means you'll get them when you do a fresh checkout of a tree, and
any time you receive a new item from the server. That's plenty of
coverage. There's just no need to marshall these invariant things to
the client during an update.

Any objections? If not, I'm just going to remove this UUID update
stuff from /trunk.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Mar 14 16:29:31 2003