Hi, all.
I'm looking at using Subversion as the backend for a content
management system, for a variety of reasons. The phrase "content
management system" generally means bells and whistles that do not
directly pertain to the Subversion code base, and which I am implementing
through CGI (by adding them to Insurrection, mostly), but there are
two exceptions:
1. Autoversioning of files uploaded through HTTP POST
Until all common browsers support WebDAV and/or XForms,
we are left with HTML Forms, which do not support the PUT
method of the HTTP/WebDAV protocols. I've already written
a CGI script in Python that combines with Insurrection to
get around the problem, but I thought I'd ask whether it would
be worthwhile to edit mod_dav_svn to accept files for autoversioning
through the POST method. Among other things, that would allow
such things as accepting log messages along with the upload,
or accepting deltas of some kind or other.
2. The GET method when applied to directories in a repository.
The SVNIndexXSLT option is nice, but it would be better if
a directory index requested by a GET would yield more information
from the properties of a directory's entries, XML formatted,
so the XSLT transform could present it in the form CMS users like
to see (things like icons selected by MIME type and the like).
It doesn't look like a difficult thing to add to repos.c in
the mod_dav_svn directory, but before I set out to do something
like that, I thought I would ask if I could do so without
breaking something in the Subversion clients. Am I right to
think that the svn client could just deal if the DTD and output
for the GET was changed?
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Feb 3 01:15:12 2007