Thanks. I had actually come across that documentation since I posted
the original question, and I am certainly finding the messaging API
simpler to use.
Can you give me any indication of when the 0.8 release will be available?
On 16/07/2010 10:36, Gordon Sim wrote:
On 07/14/2010 03:05 PM, Chris Howard wrote:
Hi,
I am currently evaluating qpid, to see if it would be suitable for use
within a load testing product. Initially, I am only interested in
running on Windows. I will need to use the C++, .NET, java and python
clients.
I am not sure whether I should be using the "messaging" API, or the
standard API. What are the pros/cons of each? There seems to be very
little documentation for the messaging API, but it does seem to provide
a simpler interface, and the fact that it is not tied to a particular
version of AMQP is a plus. Is there any functionality that is not
available through this API?
There is some expanding documentation available[1]. In addition to JMS
and WCF, the Qpid API is available now in python, c++ and .NET. The
addressing scheme it uses can now also be used in conjunction with the
JMS client.
The API and addressing is now stable in so far as we don't anticipate
changes that would break backwards compatibility and I think would be
the recommended API from the next release (which will be 0.8) onwards.
However there have been such changes since the 0.6 release.
[1]
http://qpid.apache.org/books/0.7/Programming-In-Apache-Qpid/html/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]
