qpid-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Justin Ross (JIRA)" <j...@apache.org>
Subject [jira] [Closed] (QPID-526) Don't use a Queue object just to convey the name of a queue .....
Date Wed, 21 Aug 2013 11:12:53 GMT

     [ https://issues.apache.org/jira/browse/QPID-526?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Justin Ross closed QPID-526.

> Don't use a Queue object just to convey the name of a queue .....
> -----------------------------------------------------------------
>                 Key: QPID-526
>                 URL: https://issues.apache.org/jira/browse/QPID-526
>             Project: Qpid
>          Issue Type: Improvement
>          Components: C++ Client
>            Reporter: Jonathan Robie
>             Fix For: 0.6
> We should use strings to represent the name of a queue, not a Queue object, which implies
that much more is going on than creating a string. The first parameter of the channel.consume()
method is one place where this should be fixed:
> Example (from a topic listener):
>         Queue message_queue("message_queue");
>         Listener listener;
>         string routingKey="routing_key";
>         channel.consume(message_queue, routingKey, &listener);
>         channel.start();
> The only reason for the message_queue object is to hold the name of the AMQP broker queue
from which messages are to be consumed, but code that creates a Queue object raises the expectation
that a queue is being created on the client side, and make it harder for users to grasp the
underlying model.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org

View raw message