You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@qpid.apache.org by Chris Howard <ch...@facilita.co.uk> on 2010/07/14 16:05:16 UTC

Should I be using the messaging API?

  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?

Also, how does the windows port of qpid compare to the linux version? 
How much has the windows version been used in the real world?

Regards,
Chris




---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project:      http://qpid.apache.org
Use/Interact: mailto:users-subscribe@qpid.apache.org


Re: Should I be using the messaging API?

Posted by Gordon Sim <gs...@redhat.com>.
On 07/16/2010 10:52 AM, Chris Howard wrote:
> 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?

We don't have an agreed date yet, I'm afraid.

I'd be in favour of doing one quite soon (as its been a long time since 
the 0.6 release was branched).

---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project:      http://qpid.apache.org
Use/Interact: mailto:users-subscribe@qpid.apache.org


Re: Should I be using the messaging API?

Posted by Chris Howard <ch...@facilita.co.uk>.
  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:users-subscribe@qpid.apache.org


---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project:      http://qpid.apache.org
Use/Interact: mailto:users-subscribe@qpid.apache.org


Re: Should I be using the messaging API?

Posted by Gordon Sim <gs...@redhat.com>.
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:users-subscribe@qpid.apache.org


Re: Should I be using the messaging API?

Posted by Gordon Sim <gs...@redhat.com>.
On 07/15/2010 04:01 PM, Kerry Bonin wrote:
> FWIW, we have a group here using it (the Python API) in a production
> system (along with the C++ API), although they did have various
> complaints, primarily around the lack of an callback model for the
> messaging API.

Perhaps worth pointing out that it is now quite easy to do your own 
dispatch to listeners on a per-session basis. E.g.

    Receiver r;
    while (session.nextReceiver(r, timeout)) {
        Callback c = get_callback(r);//e.g. this method might use the 
receivers name to lookup a registered callback
        c(r.fetch(Duration::IMMEDIATE));
        session.acknowledge();
    }

A similar pattern works for python also. The benefit of this is that it 
allows flexibility in how timeouts and acknowledgements work etc without 
imposing a great deal of effort on the user.

I do think that what is offered out-of-the-box here so to speak can be 
expanded. One of the next steps with the API is to look at a more 
generic mechanism for polling/waiting for events of interest (not just 
receipt of messages, but receipt of confirmations etc also). Moving past 
the requirement for thread-per-session would be one goal here. I think 
that work would also be a good route to defining utilities for message 
dispatch.

Would be good to get feedback on any of the other complaints to see if 
we can address them. (Your feedback on bugs in the past has been much 
appreciated!).

---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project:      http://qpid.apache.org
Use/Interact: mailto:users-subscribe@qpid.apache.org


Re: Should I be using the messaging API?

Posted by Kerry Bonin <ke...@gmail.com>.
FWIW, we have a group here using it (the Python API) in a production
system (along with the C++ API), although they did have various
complaints, primarily around the lack of an callback model for the
messaging API.

On Thu, Jul 15, 2010 at 5:03 AM, Chris Howard
<ch...@facilita.co.uk> wrote:
>  Thanks for the information. How mature is the python messaging API though?
> It is referred to in the 0.6 documentation as a "candidate" API, and there
> is also a list of areas that still need work. Is this client suitable for a
> production system?
>
> On 14/07/2010 19:32, Alan Conway wrote:
>>
>> On 07/14/2010 10:05 AM, 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?
>>
>> You should go with the messaging API, the old API will be deprecated and
>> eventually removed.
>
>
> ---------------------------------------------------------------------
> Apache Qpid - AMQP Messaging Implementation
> Project:      http://qpid.apache.org
> Use/Interact: mailto:users-subscribe@qpid.apache.org
>
>

---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project:      http://qpid.apache.org
Use/Interact: mailto:users-subscribe@qpid.apache.org


Re: Should I be using the messaging API?

Posted by Chris Howard <ch...@facilita.co.uk>.
  Thanks for the information. How mature is the python messaging API 
though? It is referred to in the 0.6 documentation as a "candidate" API, 
and there is also a list of areas that still need work. Is this client 
suitable for a production system?

On 14/07/2010 19:32, Alan Conway wrote:
> On 07/14/2010 10:05 AM, 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?
>
> You should go with the messaging API, the old API will be deprecated 
> and eventually removed.


---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project:      http://qpid.apache.org
Use/Interact: mailto:users-subscribe@qpid.apache.org


Re: Should I be using the messaging API?

Posted by Alan Conway <ac...@redhat.com>.
On 07/14/2010 10:05 AM, 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?

You should go with the messaging API, the old API will be deprecated and 
eventually removed.


---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project:      http://qpid.apache.org
Use/Interact: mailto:users-subscribe@qpid.apache.org