[Xesam] Need paged search mode for xesam

[Jos van den Oever]

> Uhm, that was not the intention :-) The hit_ids argument is an arbitrary
> array of hit ids, fx, [1, 7, 28]. It is meant to make it convenient to react
> to HitsModified or the user selecting a collection of elements in a ui.
>
> I am open for making it sequential access though (even though this would be
> an API break). This would possibly result in a lot of dbus traffic if I move
> a dir with the Linux kernel source and the server emits HitsModified for all
> the files (and my app would need to call GetHitData on all affected hits -
> which are unlikely to have sequential ids).

It was my impression that all hits are numbered starting from 0. So if
HitsAdded() is emitted once with value 3, I can access data for hits
0, 1 and 2. Perhaps this should be clarified in the spec.

Of course when calling GetHitdata, you can pass e.g. (2,0,1).

Cheers,
Jos