You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2017/10/03 18:26:00 UTC
[jira] [Commented] (DISPATCH-845) Allow connecting containers to
declare their availability for link routes
[ https://issues.apache.org/jira/browse/DISPATCH-845?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16190102#comment-16190102 ]
ASF GitHub Bot commented on DISPATCH-845:
-----------------------------------------
GitHub user ted-ross opened a pull request:
https://github.com/apache/qpid-dispatch/pull/204
DISPATCH-845 - Added connection-scoped link-route destinations.
Link route destinations can be dynamically created for a connection based on a connection property in the OPEN frame. The lifecycle of the link-route addresses tracks the connection.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/ted-ross/qpid-dispatch tross-DISPATCH-845
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/qpid-dispatch/pull/204.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 #204
----
commit a7752a37f3c2f6ce5e1df3377d2a5173b9e9324a
Author: Ted Ross <tr...@redhat.com>
Date: 2017-10-03T18:22:58Z
DISPATCH-845 - Added connection-scoped link-route destinations.
----
> 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: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org