Stefan Küng <tortoisesvn_at_gmail.com> wrote on 20.03.2008 22:24:16:
> > * increased delay until the log gets shown
> > (about 1 sec on a low latency network)
> > * no off-line access to the log
> > (TSVN should not show the "Go Off-line?" dialog)
> >
> > I think this is acceptable for the svnbridge use-case for now.
> > Please let me know if it solved your issues. If that is the case,
> > the code can be reworked to eliminate most of the limitations.
>
> There's another (small) problem if multiple repositories have the same
> URL, and that problem is inside Subversion: a checked our working copy
> also has that URL assigned.
Right. SvnBridge would need a way to tell them apart automagically.
However, that would make the whole point of being able to use standard
SVN tool moot.
> Subversion uses that URL internally for some working copy operations
> (i.e., copy/move, and I think some others too). Now, as long as the
> users know which working copies are from which repository, that should
> not be a problem. But with nested layouts (one working copy folder from
> repo A inside a working copy folder from repo B) this could get nasty.
> Because Subversion could then not see that these working copies belong
> to different repositories (FYI: not all working copies have the
> repository UUID saved - the UUID is usually only used for direct repo
> access, not for working copy operations). That means users you do an
> svn cp wcfromRepoA\wcfromRepoB\file wcfromRepoA\file
> Yes, that's also possible with different URLs, but if those have the
> same URLs then Subversion won't notice this even when committing (now,
> the commit will fail).
And there may be cases where something works fine with an 1.5 client
against 1.5 servers but fails miserably with older or future versions.
Perhaps, I should ask on the SVN mailing list what guarantees they think
should be given. For instance, copied repository "templates" can result
in multiple repos with the same UUID. Dump / filter / load modifies
the history etc.
Maybe they can agree on a set of procedures that are considered 'harmful'
and will be documented as such plus a way to detect other changes
reliably.
As long as there is some unique key (e.g. URL + UUID), we can easily adapt
the log cache to that scheme.
> So I suggest a change to SvnBridge:
> instead of connecting to http://localhost:8081/Projectname, have the
> users connect to http://localhost:8081/server.com/Projectname - that way
> the URLs will not be the same for all servers, and it will prevent a lot
> of subtle problems.
Yes, that seems the way to go.
I think we should wait for feedback from the SvnBridge people and
then decide whether or not to drop the option in RC1. The default
would be 'drop it' although it shouldn't do harm to keep it.
-- Stefan^2.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe_at_tortoisesvn.tigris.org
For additional commands, e-mail: dev-help_at_tortoisesvn.tigris.org
Received on 2008-03-23 18:40:13 CET