I have a handful comments about this (Jos also asked about the same on IRC recently). It was in fact a design decision, but i am writing this from my mobile since I'm on holiday, so I'll elaborate when I get home tuesday.
Cheers, Mikkel 2008/5/2, Jamie McCracken <[EMAIL PROTECTED]>: > For a serch gui its essential to page results using an offset and limit > to define the page size > > currently xesam api lacks the offset component (although it has a limit) > > there are several workarounds: > > 1) add a hit.offset property > 2) add new api : GetPagedHits (in string search, in int PageStart, in > int PageEnd, out aav results) or similar > 3) add a hit.pagesize property and have GetNextpage/getPrevPage methods > > Anyway we desperately need this to make things fast otherwise putting a > huge result set over dbus is gonna be awfully slow > > jamie > > > > _______________________________________________ > Xesam mailing list > [email protected] > http://lists.freedesktop.org/mailman/listinfo/xesam > _______________________________________________ Xesam mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/xesam
