Are you thinking of a table that defines mappings between XDM / XML
Schema types and AMQP types, and another table doing the same for SQL?
That would certainly be extremely helpful, in the XML Exchange, I'm
treating message properties as untyped for now simply because at the
time I didn't have time to create such a table.
Or are you thinking of something that would involve coordinating the
type systems?
Jonathan
John O'Hara wrote:
Getting the type system between SQL and XDM lined up in the AMQP spec is an
important part to making this simple going forward.
Would be interested in what Jonathan thinks....
John
2009/2/20 Alan Conway <[email protected]>
Jonathan Robie wrote:
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).
Boost provides convenience libraries that making implementing istream
fairly easy. It shouldn't be hard to write an istream impl that iterates
over message content. Take a look at
http://www.boost.org/doc/libs/1_38_0/libs/iostreams/doc/index.html
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:[email protected]
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:[email protected]
