2006/12/3, Jos van den Oever <<a href="mailto:jvdoever@gmail.com">jvdoever@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;">
2006/12/3, Joe Shaw <<a href="mailto:joeshaw@novell.com">joeshaw@novell.com</a>>:<br>> Mikkel Kamstrup Erlandsen wrote:<br>> > Just a quick idea,<br>> ><br>> > How about using JSON (<a href="http://www.json.org">
www.json.org</a> <<a href="http://www.json.org">http://www.json.org</a>>) as to<br>> > represent the query objects (instead of xml)?<br>><br>> I'm reluctant to do this because I'm not sure how comprehensive the
<br>> stacks are for C#. The XML stacks we have -- the built in one in Mono,<br>> or libxml2 for C -- are very mature parts of the platforms.<br>><br>> > It is light, easily readable, widespread, and there is possibility to
<br>> > write extremely fast parsers.<br>><br>> Maybe, but we should be focusing our efforts on building the search<br>> software, not on hot-serialization-technology-of-the-day parsers.<br><br>I agree. Lets just say that the simple interface cannot have nested
<br>queries, in other works, no brackets. Then it is possible to use dbus<br>for specifying the query object.</blockquote><div><br>I'm not sure I follow you. What do you mean by "use dbus for specifying the query object" ?
<br><br>Cheers,<br>Mikkel<br></div><br></div>