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

Ken Giusti resolved QPID-4063.
------------------------------

       Resolution: Fixed
    Fix Version/s: 0.18

http://svn.apache.org/viewvc?view=revision&revision=1351518
http://svn.apache.org/viewvc?view=revision&revision=1351519

Forgot to resolve this - thanks Ted for the reminder!
                
> Allow user to assign the name of the source queue when creating an exchange 
> or dynamic route.
> ---------------------------------------------------------------------------------------------
>
>                 Key: QPID-4063
>                 URL: https://issues.apache.org/jira/browse/QPID-4063
>             Project: Qpid
>          Issue Type: New Feature
>          Components: C++ Broker
>    Affects Versions: 0.17
>            Reporter: Ken Giusti
>            Assignee: Ken Giusti
>            Priority: Trivial
>             Fix For: 0.18
>
>         Attachments: QPID-4063.txt
>
>
> When a federation route is created - either an "exchange" or a "dynamic" 
> route - a dedicated queue is created on the source broker.  This queue is 
> used to hold messages that are forwarded to the remote broker.
> This queue is created by federation, and assigned a (somewhat) randomized 
> name.
> It should be possible - as an option - to allow the user to specify the name 
> for that queue.  This would be useful for a couple of reasons... 
> 1) Monitoring the state of the queue would be easier if it had a meaningful 
> name.
> 2) "Power Users" could specify an existing queue, which could then be used as 
> a target for messages that should be forwarded over the federation, 
> 3) Allow several routes share the same queue (if msg ordering need not be 
> preserved) to fan out work across a federation.
>  

--
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: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to