Martin,
Correct me if I have stated this incorrectly. The problem we are dealing
with now is that when we run the JavaHL command to fetch the statuses (the
equivalent of svn status -u) we get back all of the incoming changes, but
the status information we get back does not include stuff like the remote
revision number and URL that we need for the Synch view. So we have to
then call svn info on each item to retrieve this? Over WebDAV, each svn
info call is probably 5 or more server roundtrips, so this is a huge
performance killer but we need it for correctness?
So what we need to do is pursue whether JavaHL can be changed to give us
this information on the initial status call?
I was experimenting with the command line. And noticed the following:
svn status -u
This provides the list of remote changes, but does not show the remote
revision number.
svn status -u -v
This provides a listing of every file, changed or not, but it does give
the remote revision number.
Perhaps if we changed out getAll boolean from false to true, we would then
get this information on the JavaHL call? Performance wise, this would be
a lot better than calling svn info although we will obviously get back
more information than we need.
Finally, when I was debugging this, I noticed that svn status is run twice
when I do a Synch. One time with contactServer = false, then again with
true. Shouldn't it only do the latter? On Windows, svn status is slow.
Mark
PS - One other thought if we cannot figure this out. Could we change our
code so that we only call svn info when the information we need is
missing? That way, if JavaHL is changed, or if say JavaSVN is able to fix
this right away, then we could get a performance boost without changing
our code.
_____________________________________________________________________________
Scanned for SoftLanding Systems, Inc. by IBM Email Security Management Services powered by MessageLabs.
_____________________________________________________________________________
Received on Fri Aug 5 23:43:47 2005