Re: [Tracker] From the client side

[Martyn Russell <martyn imendio com>]

On 23/11/08 14:49, Jamie McCracken wrote:
> On Sun, 2008-11-23 at 15:26 +0100, Mikkel Kamstrup Erlandsen wrote:
> > 2008/11/21 Marko Anastasov<marko anastasov gmail com>:
> > > Hey all,

Hi :)

> > > A few questions:
> > >
> > > In practice, pulling every single document's (whatever type) metadata
> > > from Tracker over D-Bus is slow. For example it takes 10+s on my 2 yr
> > > old machine to gather information for about ~1000 documents.
> > > How do you see this problem?
> > Why is it that you need to do that? I mean in practice one should
> > never keep more than a "sliding window + cache" in memory on the
> > client side. Fx. the 15 visible documents + 30 backwards and forwards
> > for fast scrolling.
>
> I agree although widget support for this might be limited or might
> require extensive hacks
>
> in near future I hope to have a direct access client to trackers sqlite
> db to avoid dbus overhead

My thought on this at the moment is that if this is needed then either 
the application developer is doing something drastically wrong or the 
client interface over DBus is just not good enough. I tend to think the 
later is the current problem given my recent application experiences 
using libtracker.

As for DBus overhead. I really don't think that overhead is going to be 
noticeable. There is only so much information a user can process at once 
on the screen and it isn't going to be faster than tracker + DBus 
overhead. If the application and client experience with tracker is done 
correctly, it should be smooth.

This highly depends on a number of factors of course.

--
Regards,
Martyn