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

Re: New basic feature ?

From: Greg Hudson <ghudson_at_MIT.EDU>
Date: 2007-08-07 20:24:50 CEST

On Tue, 2007-08-07 at 12:21 -0400, John Peacock wrote:
> svnserve only knows there is a repository when it goes to the requested
> path and checks for the special repos files. There is no concept such
> as ParentPath for svnserve, since it is specifically designed so that it
> doesn't have to run resident (it can be started via [x]inetd or ssh
> invocation under *nux).

If you're running it as a daemon, you can specify a root path which is
functionally similar to ParentPath.

The feature Franck is asking for is certainly possible to implement. It
would be a little ugly since the RA layer currently traffics in
repository URLs. The new API would have to invent some related concept
like a stub repository URL, which doesn't identify a repository but does
give enough information to identify some kind of directory. "svn
list-repositories svn://myserver.example.com" (or whatever) would go and
make a repository-list request to that server. With the server properly
configured, you'd get back a list of repository root URLs.

On a protocol level, the ra_svn handshake would need to be extended,
since in the current scheme of things you've already identified a
repository once the handshake is complete.

I wouldn't really favor adding this feature; it feels muddy and is
handled pretty easily out of band. But it shouldn't be dismissed out of
hand as not making sense.

> Since you've exposed the fact that you are
> running Windows, you are likely to always be running svnserve as a
> service, so that distinction doesn't apply.
>
> > I'm asking this because I don't take a look to Server code but I think that
> > can be added either
> > 1- easily if server check all repositories at startup and keep them in
> > memory
>
> There is no such thing as "all repositories" since svnserve specifically
> allows you to access repositories *anywhere* in the filesystem, not just
> under some given directory. As I tried to indicate earlier, the only
> configuration available to svnserve is the conf directory inside the
> actual repositories themselves. The Apache server has an external
> config file, which is why SVNParentPath is possible.
>
> John
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Aug 7 20:23:11 2007

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.