[
https://issues.apache.org/jira/browse/DISPATCH-230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15178255#comment-15178255
]
ASF subversion and git services commented on DISPATCH-230:
----------------------------------------------------------
Commit e9da4b7ab0f89a35436ca1af50821a6f3e3b5f52 in qpid-dispatch's branch
refs/heads/tross-DISPATCH-179-1 from [[email protected]]
[ https://git-wip-us.apache.org/repos/asf?p=qpid-dispatch.git;h=e9da4b7 ]
DISPATCH-230 - Added route-container role and deprecated on-demand role.
> New connection role: route-container
> ------------------------------------
>
> Key: DISPATCH-230
> URL: https://issues.apache.org/jira/browse/DISPATCH-230
> Project: Qpid Dispatch
> Issue Type: Improvement
> Components: Router Node
> Reporter: Ted Ross
> Assignee: Ted Ross
> Fix For: 0.6
>
>
> This feature introduces a new connection role "route-container" that replaces
> the now deprecated "on-demand" role. The on-demand role was only relevant to
> connectors (outgoing connections). The new route-container role may be used
> in both connectors and listeners.
> Connections that have the role "route-container" are eligible for use in
> waypoints and link-routes (i.e. they may be referenced in routes that define
> waypoints and link-route destinations). This allows for the possibility that
> brokers may be configured to initiate connections to the router.
> The on-demand role will remain available in the configuration syntax. It
> will be internally translated to route-container.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
