DAV SVN-ACTIONs vs svnserve commands

If somebody adds svnserve logging, it probably makes sense to base the
logged actions off of the svnserve main command set.

It also probably makes sense to keep the output similar to the DAV
operational log, which defines its own set of names for actions
(SVN-ACTION).

epg already made backwards-incompatible changes to the DAV operational
log format for 1.5. I think we should consider continuing along those
lines (in 1.5) by eliminating needless differences between these two
sets of actions names. Here's a summary:

SAME
commit
lock
unlock
get-mergeinfo
log
replay
switch
update

EASY TO CHANGE (DAV log => svnserve command)
list-dir => get-dir
revprop-change => change-rev-prop
revprop-list => rev-proplist
blame => get-file-revs
remote-status => status (I think)
diff-or-merge => diff

MORE COMPLEX (DAV vs svnserve)
prop-list vs get-file/get-dir
checkout-or-export (really just update, but it deduces this *after*
the report is sent)

SVNSERVE COMMANDS NOT LOGGED BY DAV
get-file (this is a conscious choice I know)
reparent (this concept doesn't really exist for DAV)
get-latest-rev
get-dated-rev
check-path
stat
get-locations
get-location-segments
get-lock / get-locks

SVNSERVE COMMANDS LIKE DAV LOGS BUT WITH DIFFERENT BATCHNESS
(ie, these should probably be folded with the similar one)
rev-prop (like rev-proplist)
lock-many (like lock)
unlock-many (like unlock)
replay-range (like replay)

I think at the very least we should change the SVN-ACTION words in the
"EASY TO CHANGE" category. I'd also consider changing prop-list to be
logged like get-dir / get-file with something on the line saying
"props=1 content=0" or something.

What do y'all think?

--dave

-- 
David Glasser | glasser@davidglasser.net | http://www.davidglasser.net/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: dev-help_at_subversion.tigris.org