[jira] [Commented] (DISPATCH-476) qualified link routing

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/DISPATCH-476?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16517339#comment-16517339
 ] 

ASF GitHub Bot commented on DISPATCH-476:
-

Github user lulf closed the pull request at:

https://github.com/apache/qpid-dispatch/pull/111


> qualified link routing
> --
>
> Key: DISPATCH-476
> URL: https://issues.apache.org/jira/browse/DISPATCH-476
> Project: Qpid Dispatch
>  Issue Type: Improvement
>  Components: Routing Engine
>Reporter: Gordon Sim
>Priority: Major
> Fix For: Backlog
>
>
> It might be useful to have the router be able to apply some matching logic 
> when doing link routing. A link could be qualified with information that the 
> router would then use to determine which connections were applicable.
> This would save having to add lots of expliclit qualified link routes.
> Another way to handle it could be to have connections identify themselves as 
> being sources/targets for link routing particular addresses. The router could 
> then automatically add link routes on processing the open of that connection.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

[jira] [Commented] (DISPATCH-476) qualified link routing

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/DISPATCH-476?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15644159#comment-15644159
 ] 

ASF GitHub Bot commented on DISPATCH-476:
-

GitHub user lulf opened a pull request:

https://github.com/apache/qpid-dispatch/pull/111

DISPATCH-476: Add support for groupId property for matching link routes and 
auto links

This is a proposed alternative for supporting a mapping of multiple 
connections - multiple link
routes/autolinks by grouping them on a 'groupId' identifier. The 
corresponding group is selected based on a connection property 
'qd.route-container-group'.

We have discussed this approach previously, and somewhat decided that we 
should take a different approach. I wanted to implement this approach as a way 
of learning more of the router internals, so consider this PR a POC that you 
can close if you think this feature is not useful, though I do think it gives a 
lot of flexibility with little increase in complexity.

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/lulf/qpid-dispatch DISPATCH-476

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/qpid-dispatch/pull/111.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #111


commit ee054ce69d21a33663152b90b876ad63cc2e839e
Author: Ulf Lilleengen 
Date:   2016-11-04T12:28:30Z

DISPATCH-476: Add support for groupId property for matching link routes and 
auto links




> qualified link routing
> --
>
> Key: DISPATCH-476
> URL: https://issues.apache.org/jira/browse/DISPATCH-476
> Project: Qpid Dispatch
>  Issue Type: Improvement
>  Components: Routing Engine
>Reporter: Gordon Sim
>
> It might be useful to have the router be able to apply some matching logic 
> when doing link routing. A link could be qualified with information that the 
> router would then use to determine which connections were applicable.
> This would save having to add lots of expliclit qualified link routes.
> Another way to handle it could be to have connections identify themselves as 
> being sources/targets for link routing particular addresses. The router could 
> then automatically add link routes on processing the open of that connection.



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

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