Hi Carl,
I think the best approach for either language is to use an
implementation that prepares queries. The two languages are not terribly
different in the way they handle conditions on headers.
I think that reading the content of the message is the slowest part of
the XML Exchange, I've roughed in code that should allow me to avoid
that for queries that do not actually access the message. (If the
exchange could access the message content as an istream, the query
engine would do this for me; as is, I have to check this by hand).
I suspect that querying the headers with a prepared query, without
reading message content, should be pretty fast, but that's something
we'll have to measure. I am gone most of next week (at the XQuery face
to face), I doubt that I'll have something ready to check in today, so
it may be a few weeks before I can check anything in.
Jonathan
Carl Trieloff wrote:
Chenta, Jonathan,
I would be interested to know if you have any thoughts on best
practices to create well optimized bindings/selector/filter for QXuery
& SQL that can operate on the headers etc of the message that are
specified using the amqp type system.
ActiveMQ does SQL 92 & XPath
http://activemq.apache.org/selectors.html
Chenta, I would expect the first set is to get it working, then make
it fast, but am wondering what are the best practices in doing query
optimization for this use-case. I wonder if Active have done any query
optimization...
Carl.
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:[email protected]
