2007/6/17, Mikkel Kamstrup Erlandsen <<a href="mailto:mikkel.kamstrup@gmail.com">mikkel.kamstrup@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;"> 2007/6/16, Mikkel Kamstrup Erlandsen <<a href="mailto:mikkel.kamstrup@gmail.com" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">mikkel.kamstrup@gmail.com</a>>:<div><span class="q"><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;"> Hi all,<br><br>While hacking on xesam-tools[1] I have struck a few problems in the current spec and I think we should settle them asap.<br><br>Please have a look at <a href="http://wiki.freedesktop.org/wiki/XesamSearchUpdates" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)"> http://wiki.freedesktop.org/wiki/XesamSearchUpdates</a> and gimme some feedback.</blockquote></span><div><br>It was just pointed out to me that the query schema in the current form does not have <tt>extendedSelectionTypes </tt> in the <tt>selectionTypes</tt> - this makes <tt>regExp</tt> and <tt>proximity</tt> selectors not allowed by the schema. I've updated <a href="http://wiki.freedesktop.org/wiki/XesamSearchUpdates" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)"> http://wiki.freedesktop.org/wiki/XesamSearchUpdates </a> with a proposal 5.</div></div></blockquote><div><br>More proposed updates. I've added a point 6 to the list at <a href="http://wiki.freedesktop.org/wiki/XesamSearchUpdates">http://wiki.freedesktop.org/wiki/XesamSearchUpdates </a>. It has to do with an inherent race condition in the search  interface. When you fire a search via NewSearch the server might start firing HitsAdded signals before you have a chance to connect to them - in fact it might start firing these signals before the call to NewSearch returns! I think this is an optimization we need. <br><br>The proposed solution is to add a StartSearch() method to the interface.<br><br>Cheers,<br>Mikkel<br></div><br></div><br>