Re: Somewhat corrupted repository: Berkeley DB Permissions errors on SVN 1.0.2

Paul Oppenheim wrote:
> So, my suggestion to you, or whoever else is following, is that since
> svn:// works with a daemon, why not have svn+ssh:// work with a daemon
> as well? Just have it act like a port-forwarded svn:// -- that's
> probably how most people expect it to work anyway.

I agree it's confusing; I believe the origin of svn+ssh:// working the way it
does is for sites where *no* extraneous daemons are permitted. As such, it is
an extension to the way that file:// protocol functions for local users. This
way, remote users use svn+ssh:// via their existing ssh keys, running the code
as themselves. And local users use file://, again running the files as themselves.

The difference is that remote users need to run a network protocol, hence the
use of svn+ssh:// for the remote client (as opposed to having file+ssh://). It
just so happens that 'svnserve -t' functions as a sort of svn:// proxy as well
as a standalone daemon.

I could certainly see a new option to svnserve to run in a true proxy mode via
tunneled connections. That would work the way you expect it to, but would
require a server daemon, so it wouldn't fit everyone's needs (anymore than the
current implementation does). The same remote svn+ssh:// URL could be used, but
it would be up to the site administrator to decide which way to go. You could
even have the svnserve proxy for some other machine running the conventional svn
daemon...hmmm....

John

-- 
John Peacock
Director of Information Research and Technology
Rowman & Littlefield Publishing Group
4720 Boston Way
Lanham, MD 20706
301-459-3366 x.5010
fax 301-429-5747
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org