> From: daniele@grinta.net [mailto:daniele@grinta.net]On Behalf Of Daniele
> Nicolodi
> Sent: 30 June 2002 17:30
> On Fri, Jun 28, 2002 at 10:53:40AM -0500, Ben Collins-Sussman wrote:
> > Daniele Nicolodi <daniele@grinta.net> writes:
> >
> > > I want to start to work on ViewSVN or something like to browse svn
> > > repositorie trought web. I want to implement svn log and svn info
> > > at the moment.
> > >
> > > What is the idea on developping that tool: parse svn command output
> > > or write python equivalens for these command using library bindings ??
> >
> > The python bindings already exist for libsvn_fs, which is all we need.
>
> libsvn_fs is only for acces repository on local filesystem or i'm wrong ??
>
> If so this mean that ViewSVN will work only if the subversion server is
> running on the same machine of viewsvn. In my opinion this is a bad think.
> What about build viewsvn around of libsvn_repo, that is network trasparent,
You mean libsvn_ra. libsvn_repos is a this wrapper around libsvn_fs, and is
therefor also only useful on the same box as the repository.
> so we can run viewsvn on a remote repository ?? Whate are the limitations
> on code over libsvn_repo instead of libsvn_fs ??
The downside of doing this through ra would be (IMHO):
- speed problems
- increased server load
- increased network traffic
I don't really see the advantage of having ViewSVN work on remote repositories.
If you really don't want ViewSVN on the same box as your main svn server, you need
repository replication... ;)
Sander
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sun Jun 30 17:42:24 2002