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

Re: [Subclipse-dev] Revision graph and cache implementation

From: Mark Phippard <markphip_at_gmail.com>
Date: Fri, 11 Jul 2008 15:53:16 -0400

On Fri, Jul 11, 2008 at 11:49 AM, Alberto Gimeno <gimenete_at_gmail.com> wrote:

> I don't know anything about the underlying API and protocol. For
> example I don't know if every time I ask for an array of log messages
> the API opens a new connection. In that case it would be better to use
> callbacks. Or for example it would be better that the number of log
> messages retrieved each time should be decided for the underlying
> protocol / API.

OK, I have exposed a new ISVNClientAdapter method you can use to
receive the log messages in a streaming manner. You will need to
create a class that implements the new ISVNLogMessageCallback
interface and pass this into the method. As the Subversion API
receives data from the server it will call the method in your class
with the data for that one message. All of the existing methods use
this internally, they simply store the messages in an ArrayList until
they are all received and then return that as an array. See the
SVNLogMessageCallback class as an example.

Anyways, the point for you is to be able to process each item as you
receive it and this will let you do that.

NOTE: when exposing this new method, I also exposed another new
feature, and that is the ability to ask for the revision properties
you want to receive. This is of no interest to you, so just pass
ISVNClientAdapter.DEFAULT_LOG_PROPERTIES for this value.

Mark Phippard
To unsubscribe, e-mail: dev-unsubscribe_at_subclipse.tigris.org
For additional commands, e-mail: dev-help_at_subclipse.tigris.org
Received on 2008-07-11 21:53:27 CEST

This is an archived mail posted to the Subclipse Dev mailing list.