[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: ra_dav Protocol for the trace_old_file_location Function

From: C. Michael Pilato <cmpilato_at_collab.net>
Date: 2004-04-08 15:30:57 CEST

Shlomi Fish <shlomif@iglu.org.il> writes:

> Hi!
> The purpose of this E-mail is to suggest a protocol for the
> trace_old_file_location function over WebDAV/DeltaV (to be
> implemented as a client in libsvn_ra_dav and as a server in
> mod_dav_svn). The function will use a REPORT request, with the
> following customized XML Body:

Adamently opposed to "trace_old_file_location". Don't box us into
this one operation, please. I'd much rather have the RA interface
called just RA->get_locations()

   svn_error_t *
   get_locations (apr_hash_t **locations,
                  const char *path,
                  svn_revnum_t peg_revision,
                  apr_array_header_t *location_revisions,
                  apr_pool_t *pool);

Allow folks to pass a path, a peg revision, and a set of location
revisions. The return hash maps those same location revisions to
the location paths.

DAV REPORT request protocol would look similar to what you suggested,
save for <S:get-locations> instead of <S:trace-old-file-location>,
<S:location-revision> instead of <S:past-revision>, and the ability
to specify many <S:location-revision> tags.

DAV REPORT response protocol would be something like:

   <S:get-location-report xmlns...>

If the PATH@PEG-REVISION doesn't exist, you get a 404. Otherwise,
revisions in which the path didn't exist simply don't show up in the

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Apr 8 15:58:32 2004

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.