On Thu, 04 Jan 2007, Justin Erenkrantz wrote:
> On Thu, Jan 04, 2007 at 10:20:42AM -0800, dlr@tigris.org wrote:
> > Ideally, we'd avoid issuing a "get-merge-info" REPORT at all when the
> > server doesn't understand it. However, this capabilities discovery
> > would have to happen in a previous request (e.g. one of the many
> > PROPFINDs we issue during a 'merge'). Any ideas on how to implement
> > that are most welcome...
>
> ra_serf could do that via an OPTIONS request (it already uses this for
> commits). mod_dav_svn would need to advertise what it's capable merge-wise
> of in response to that, but that should be possible. -- justin
Cool! Would that be less expensive than simply trying the custom
"get-merge-info" REPORT, or would it be more overhead be an additional
HTTP request would be necessary when mod_dav_svn is supportive of the
REPORT (though, one more request might just be a drop in the bucket
;)?
- application/pgp-signature attachment: stored
Received on Thu Jan 4 20:18:05 2007