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

Re: DAV lock-token decisions. (please read)

From: Julian Reschke <julian.reschke_at_gmx.de>
Date: 2005-01-20 10:08:17 CET

Ben Collins-Sussman wrote:
> ...
> Mike Pilato has an idea, though I'm not sure how I feel about it. He
> thinks that if the final MERGE request gets an error regarding header
> limits, it can re-try the commit using a new custom REPORT request.
> Kinda icky.
> Feelings? Should I just bite the bullet and implement a new custom
> REPORT? I wonder if ra_dav shouldn't just use the new REPORT-type
> whenever lock-tokens are present.
> ...

Please do not use REPORT for operations that have side effects (see
RFC3253, section 3.6). Faced with a similar issue in our server (yes,
it's also a RFC3253 server :-), we choose to use POST and just adopted
the message formats used in REPORT.

> ...

Best regards, Julian

<green/>bytes GmbH -- http://www.greenbytes.de -- tel:+492512807760
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Jan 20 10:09:42 2005

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.