Simple search API proposal, take 2

[Mikkel Kamstrup Erlandsen]

Proposed Updates for the Simple API:
--------------------------------------------------------------

 - Change GetHitProperties (in s query_handle, in i offset, in i limit, in
as props, out a{sa{sas}}) to GetHits(in s query_handle, int i offset, int i
limit, in as props, out aas) where the output is on the form [[HitId, props
in rq. order], [HitId, props in rq. order], ...]. This seemed to be the
consensus of the recent discussions.

Stuff to Think About:
---------------------------------------------------
 - Ordering : Is it fair to expect ordered results from the indexer at all?
>From the new return type of of GetHits I would assume that the result set
was ordered. This may be fine in the simple api, but if we want to use the
same  data structures in the live api it is beginning to look weird. Hits
with a really high score might be added after all hits have otherwise been
retrieved. Also in the new query xml language you can actually specify an
ordering (and grouping) - does this make sense at all?

 - Moving ShowConfiguration() to org.freedesktop.search.ui.ShowConfiguration()?
A drawback is that we can't guarantee that search.simple and search.ui is
owned by the same d-bus services. If we had a search.ui we could also add a
search.ui.ShowSearchTool(in s search_string).

Cheers,
Mikkel
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.freedesktop.org/archives/xdg/attachments/20070117/1ff18e78/attachment.htm