[Xesam] Need paged search mode for xesam
Mikkel Kamstrup Erlandsen
mikkel.kamstrup at gmail.com
Wed May 7 06:19:37 PDT 2008
2008/5/7 Jos van den Oever <jvdoever at gmail.com>:
> > 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
> > 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
> > an API break). This would possibly result in a lot of dbus traffic if I
> > a dir with the Linux kernel source and the server emits HitsModified for
> > 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).
Ah, good. Then you are right. I am just trying to confuse you ;-)
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Xesam