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

Jakub Scholz updated DISPATCH-155:
----------------------------------
    Attachment: DISPATCH-155.patch

The attached patch extends the identity of connectors and listeners with their 
name. This allows to have two connectors to the same host / port from the same 
router (for example because each is using different authentication details). 
This might not be needed for listeners (where one can listen on each host/port 
combination only once) - if desired I can update the patch to affect only the 
connectors and use the original identifier for listeners.

I would appreciate if someone could have a look at it before the 0.6.0 release 
is finalized.

> Allow multiple connectors to the same broker
> --------------------------------------------
>
>                 Key: DISPATCH-155
>                 URL: https://issues.apache.org/jira/browse/DISPATCH-155
>             Project: Qpid Dispatch
>          Issue Type: Bug
>    Affects Versions: 0.4
>            Reporter: Jakub Scholz
>         Attachments: DISPATCH-155.patch
>
>
> In some use cases it might make sense to have multiple connectors configured, 
> which connect to the same broker. This makes sense for example when each 
> connection is using different credentials, where each set of credentials has 
> different access rights on the broker.
> Unfortunately, after DISPATCH-95, the identity of connectors is always 
> generated only using the address and port. As a result, you cannot have two 
> connectors to the same broker.
> It would be great if the identity of connectors could be based not only on 
> address and port but also include something more unique. Either a counter as 
> it was before or for example the connector name, which has to be unique 
> anyway.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to