[
https://issues.apache.org/jira/browse/DISPATCH-845?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16190104#comment-16190104
]
ASF GitHub Bot commented on DISPATCH-845:
-----------------------------------------
Github user ted-ross commented on the issue:
https://github.com/apache/qpid-dispatch/pull/204
Note that this feature is targeted at the 1.1.0 release.
> 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
> 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
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
