simple search api (was Re: mimetype standardisation by testsets)
Jean-Francois Dockes
jean-francois.dockes at wanadoo.fr
Sat Jan 6 07:18:09 PST 2007
> To put matters short: You agree with Magnus' proposal 2 in the thread
> "Simple ssearch API proposal, take 2"?
To put matters short :) yes
I also agree with you that it might be better to have an opaque string as
search identifier, this doesn't change anything for the application and
gives more freedom to the backend (yeah).
I also don't see why a map of maps is needed for the response in:
GetHitProperties ( in i search, in i offset, in i limit,
in as properties, out a{sa{sas}} response )
We're requesting a slice in the sequence of hits, so I guess a
sequence/array of maps should be enough. But this is not important, and
it's just a question of keeping things as simple as possible.
You might note that it is quite close to my earlier proposal of:
Query (in s query, in i offset, in i limit, in as properties, out aa{ss} hits)
(we didn't have the opaque query identifier yet at the time).
Regards,
J.F. Dockes
More information about the xdg
mailing list