2007/7/18, Fabrice Colin <<a href="mailto:fabrice.colin@gmail.com">fabrice.colin@gmail.com</a>>:<div><span class="gmail_quote"></span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
On 7/16/07, Mikkel Kamstrup Erlandsen <<a href="mailto:mikkel.kamstrup@gmail.com">mikkel.kamstrup@gmail.com</a>> wrote:<br>> I have a few suggestions for updates to the xesam search spec.<br>><br>> * API:<br>
> Remove the session properties search.blocking and search.live. These seemed<br>> to cause more confusion than I anticipated. These can be emulated in the<br>> client side lib as far as my scribblings can tell. Anoter solution might
<br>> just be better documentation of course...<br>><br>+1 from me.<br><br>> What this would mean for the api methods:<br>> * GetHits should always block until the requested number of hits has been<br>> found or the entire index has been searched (in which case the SearchDone
<br>> signal will be emitted too).<br>> * CountHits should always block until the entire index has been searched<br>> * No other methods should block<br>><br>Okay.</blockquote><div><br>Good, I shall try and punk people on IRC to get more opinions on this.
<br></div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">> * Query Language:<br>> I suggest we remove the "type" attributeon the query element. You can just
<br>> specify the Category- or StoredAs fields in you selectors.<br>><br>What are these ? I can't find either in the xsd file.</blockquote><div><br>They are fields in the upcoming ontology :-) Sorry for the obscure reference. So the idea is to replace
<br><br><query type="Foo"><br>MY-QUERY-XML<br></query> <br><br>with<br><br><query><br> <equals><br> <field name="xesam:category"/><br> <string>Foo</string>
<br> </equals><br></query><br></div><br>it is more verbose but is also more coherent with the rest of the spec.<br><br>What do you think about the idea that the server was free to forget hits as soon as they are read if
search.live == false? Which as said before would imply that GetHitData should probably return an empty list if search.live == false.<br><br>Cheers,<br>Mikkel<br></div><br>