"Akin, Klaus" <Klaus.Akin@infor.de> wrote on 03/17/2005 05:27:37 AM:
> I've Debuged my Problem further.
> With the Function getLogMessages in the Interface ISVNClientAdapter and
all of
> its implementations, the Log message are fetch with the svn-argument -v.
> This means, that to all LogMessage the affected Paths are loaded. In a
large
> or very long repository this can produce a OutOfMemory Exception and
very long
> waiting time. The Question is, is it really neccassary to load all the
> information to all Log messages at this time.
> Is there no possibility to load the affected Paths on Demand? So less
trafic
> is produced and the waiting times for a result are much shorter, if the
application
> loads only the affected Paths, which I will see on the screen.
The log API is a little richer in 1.2. I plan on looking at ways to
enhance this then. The main enhancement is that it will allow us to
retrieve a specific number of messages. So we could retrieve just the
last 20 messages and have an option to get more. That should make it
faster in general and use less memory.
I do not think that retrieving the paths on demand is feasible unless we
changed the view to only show the log message with a separate option to
show a dialog with all of the details. That is a possibility, but it
would be a bigger change and I am sure that some people would not like it
working that way.
Mark
_____________________________________________________________________________
Scanned for SoftLanding Systems, Inc. by IBM Email Security Management Services powered by MessageLabs.
_____________________________________________________________________________
Received on Fri Mar 18 01:32:28 2005