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

Re: [feature] Log HTTP header for autoversioning

From: Max Bowsher <maxb_at_ukf.net>
Date: 2005-01-13 19:36:47 CET

Stephen Haberman wrote:
> Hi,
> I wanted to file a feature request and am following the Issue Tracker
> directions (first posted to users, then Ben Collins-Sussman requested I
> repost it here).
> Short description:
> HTTP PUT autoversioning looks for an optional "Log" HTTP header to use
> instead of the generic log message.

Is there any kind of support for this in internet standards?

If not, I think it needs to be "X-SVN-Log".

> Rationale:
> Every so often, I've wanted to get things into and out of a svn repo with
> Python. I've looked at SubWiki, the svn bindings, etc., and know those
> things are possible, but I've found the simplest solution to just be HTTP
> GETs/PUTs.
> Integrated with py-curl to handle ssl and digest auth, in ~8 lines of code
> (~4 of those being setting ssl/digest options on py-curl), I can get a
> single file into and out of svn with great ease. For my simple purposes,
> this is really cool.
> My only gripe is the auto-generated log message that result from PUTs. I
> get
> that the generic log message is a fine first step and Autoversioning in
> and
> of itself is darn neat.
> But meaningful log messages would make it even better, and I thought a
> "Log"
> HTTP header would be easy for me to drop into a py-curl PUT request and
> easy
> for mod_dav_svn to get back out.
> Other notes:
> I came across someone else using HTTP PUT and having problems with setting
> svn:mime-type properties. Perhaps a general mechanism for setting both
> file
> properties and the log message from HTTP headers could be rolled into
> mod_dav_svn.
> I don't care about the actual name of the header - e.g. perhaps X-SVN-Log
> is
> more appropriate - I don't know.
> This doesn't sound like rocket science, so I ViewCVS'd into the
> mod_dav_svn
> code to see what I could make of it. Unfortunately, Java and Python have
> made me soft. Structs, bit brigades, and batons are forcing me to file
> this
> as a [feature] rather than a [patch].

The basic log message support seems reasonable, and fitting with the general
theme of DAV interoperability with traditional HTTP PUT clients.

I'm not so sure about the properties though. I'm tempted to say "use DAV
I really don't want to reinvent a subset of DAV#s functionality within PUT
I could be persuaded, though, if enough people think that the setting of
properties within PUT requests isn't the top of a slippery slope.

> Does this sound like a feature request I should put into the issue
> tracker?

Wait for some more opinions, but tentatively, for at least the X-SVN-Log
part, yes.


To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Jan 13 19:38:28 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.