[
https://issues.apache.org/jira/browse/DISPATCH-845?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16346891#comment-16346891
]
ASF GitHub Bot commented on DISPATCH-845:
-----------------------------------------
GitHub user ted-ross opened a pull request:
https://github.com/apache/qpid-dispatch/pull/252
Tross dispatch 845 1
Add automatic link-routes via a connection property. See
https://issues.apache.org/jira/browse/DISPATCH-845
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/ted-ross/qpid-dispatch tross-DISPATCH-845-1
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/qpid-dispatch/pull/252.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 #252
----
commit cdf2c99071811d42891d7a8b7e5d4acd21819ad8
Author: Ted Ross <tross@...>
Date: 2017-10-03T18:22:58Z
DISPATCH-845 - Added connection-scoped link-route destinations.
commit 8a323bd614195b6098e1962dcd1845c0d4cee098
Author: Ted Ross <tross@...>
Date: 2017-10-03T18:29:31Z
DISPATCH-845 - Added test
commit 193df0c7f3e1a21b951580b576b8da0de0c04aaa
Author: Ted Ross <tross@...>
Date: 2018-01-02T19:27:16Z
DISPATCH-845 - Fixed bug in properties traversal. A symbol value caused an
infinite parse loop.
commit b7fc23bd328b6e6dcc2f20334a4f1bdcf0e18553
Author: Ted Ross <tross@...>
Date: 2018-01-31T14:17:47Z
DISPATCH-845 - Added documentation update
----
> Allow connecting containers to declare their availability for link routes
> -------------------------------------------------------------------------
>
> Key: DISPATCH-845
> URL: https://issues.apache.org/jira/browse/DISPATCH-845
> Project: Qpid Dispatch
> Issue Type: New Feature
> Components: Router Node
> Reporter: Ted Ross
> Assignee: Ted Ross
> Priority: Major
> Fix For: 1.1.0
>
>
> In the case where a container wishes to connect to a router network and
> accept incoming routed link attaches (i.e. become a destination for link
> routes), it is now quite complicated to do so. First, the connected router
> must be configured with a listener in the route-container role. Second,
> there must be linkRoute objects configured for each prefix or pattern for the
> connected container.
> A more efficient mechanism for dynamic/ephemeral link routes can be supported
> as follows:
> * A container opening a connection to the router may provide a connection
> property that contains a list of prefixes and/or patterns for link routes.
> * During the lifecycle of that connection, the router maintains active
> link-route addresses targeting that container.
> This feature allows for lightweight establishment of link-route destinations
> without the need for connection roles and configured link-routes with
> independently managed lifecycles (active, inactive, etc.).
--
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
