[jira] Resolved: (QPID-526) Don't use a Queue object just to convey the name of a queue .....

["Alan Conway (JIRA)" <qp...@incubator.apache.org>]

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

Alan Conway resolved QPID-526.
------------------------------

    Resolution: Fixed

> 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
>
> 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.
-
You can reply to this email to add a comment to the issue online.