building a separate server for subversion, allowing subversion to focus
entirely on just repository functions and become a repository engine only
(not a bad thing). What if any is the performance hit where the server would
be used as a regular web server as well? Or is the assumption that a mod_dav
enabled server is dedicated for subversion only. Would there ever be a need
to have a non-Apache type of server for the repository and require a
separate subversion protocol to access it?
the conversion effort. But there also has to be back end conversions as well
to import from other repositories into subversion. A least one from CVS to
subversion to start with.
On your final thought: Existing clients that don't support WebDav needing
some type of proxy to WebDav ... hmm .. I like it.
----- Original Message -----
From: Greg Stein <email@example.com>
Sent: Monday, May 15, 2000 1:23 AM
Subject: Re: [subversion-dev] Subversion meeting in San Francisco,
9amWednesday 17th May
> On Fri, 12 May 2000, Patrick Bihan-Faou wrote:
> > Antoher thing I would like to play with is some sort of server plug-ins
> > offer files from a subversion DB to CVS clients of webdav clients or
> > things as they mature... From what I can see, it should be possible to
> > at least the level of functionality of "older" protocols. This would be
> > great migration path for a lot of people.
> I agree with you on this one :-) ... My hope for subversion is to see it
> use WebDAV for the protocol, Apache/mod_dav for the server, and mod_dav's
> plugin mechanism to talk to the subversion repository.
> It seems like it would be possible to write a CVS protocol to WebDAV proxy
> thingy. Dunno what priority that I would give it, but I've got to believe
> somebody out there is up for doing it.
> Greg Stein, http://www.lyra.org/
Received on Sat Oct 21 14:36:04 2006