I'm sure this topic has come up a million times. Here is one discussion I
found in the archives:
http://subversion.tigris.org/servlets/ReadMsg?list=dev&msgNo=13460. Still,
I'd like to make my comments on the bikeshed...
Are there plans to develop a remote access method that is not based on
Apache, WebDAV, and deltaV? It seems odd to me that a project intent on
displacing CVS has chosen not to support a single remote access method
supported by its predecessor.
There are many situations where access to the repository via Apache just
isn't feasible. You may not have control over which web server is intalled,
or which options/libraries are included. You may not be allowed to place
content in a web-visible location. You may have a tight review and approval
process for content accessed through a web server, where content accessible
via a shell has a less stringent review policy. You may not be allowed to
make the required adjustments to the firewall. It may be more practical for
you to get shell accounts for your team than to get the appropriate web
security in place. Etc, etc.
The bottom line for me is that my project will not be able to use Subversion
until remote access is possible with an access protocol other than ra_local
and ra_dav. I have other concerns as well, but this is an absolute
show-stopper for my organization. I believe that the tight coupling between
web server and repository is a HUGE negative, one that will allow CVS to
retain the upperhand for many (if not most) of those currently hosting a CVS
repository.
I get a kick out of this comment from the documentation:
> Feel like writing a new network protocol for
> Subversion? Just write a new library that
> implements the RA API!
LOL! That's quite a big JUST.
Thanks,
Darryl
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Aug 29 22:43:25 2002