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

Issue #1093 APIs Change

From: Shlomi Fish <shlomif_at_vipe.stud.technion.ac.il>
Date: 2003-11-01 21:07:10 CET

One thing that is clear now, is that we will have to trace the history of
a file from its peg revision down to the revision to compare. The question
has arised where should we do it:

1. In the client side, above the repository access layer.

2. In the server side in libsvn_repos.

Now #1 would be simpler to implement and won't break compatibility.
However it will cause two log commands to be have to be performed over the
network, which will slow things down considerably. This violates
Subversion's "time is proportional to operation's cost" principle.
Furthermore, the history that is traced in option #2 will have to be
somehow traced in option #1, and we might as well not do it over the

But it does break compatiblity.

A good compromise may be to add a new operation to trace the history of
files in a flexible way to the ra layer. This is of course, if there isn't
any way to already do it with the current schemes of things.

I favour option #2 for the time being and ghudson backed me up. Two very
prominent figures whom we talked with on #svn, were not fond of the idea,
though. What do you think?


        Shlomi Fish

Shlomi Fish shlomif@vipe.technion.ac.il
Home Page: http://t2.technion.ac.il/~shlomif/

An apple a day will keep a doctor away. Two apples a day will keep two
doctors away.

        Falk Fish

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Nov 1 21:07:47 2003

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.