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

ASF subversion and git services commented on DISPATCH-1145:
-----------------------------------------------------------

Commit ff60b36af18a150e59f46662ec5ec4bcc7bc82da in qpid-dispatch's branch 
refs/heads/master from [[email protected]]
[ https://git-wip-us.apache.org/repos/asf?p=qpid-dispatch.git;h=ff60b36 ]

DISPATCH-1145 - Add proper handling of multiphase addresses in edge connections.
This includes a new feature to allow containers to declare themselves as 
waypoints
during the attach phase.  This permits waypoint behavior without using 
autolinks.


> Edge Router - Implement address proxy component
> -----------------------------------------------
>
>                 Key: DISPATCH-1145
>                 URL: https://issues.apache.org/jira/browse/DISPATCH-1145
>             Project: Qpid Dispatch
>          Issue Type: New Feature
>          Components: Router Node
>            Reporter: Ted Ross
>            Assignee: Ted Ross
>            Priority: Major
>             Fix For: 1.5.0
>
>
> The Address Proxy is a component of the Edge Router module. It runs only on 
> an edge router. It has two main responsibilities:
> Address Proxy has three main responsibilities:
> # When an uplink becomes active, the "_uplink" address is properly linked to 
> an outgoing anonymous link on the active uplink connection.
> # When an uplink becomes active, an incoming link is established over the 
> uplink connection that is used to transfer deliveries to topological 
> (dynamic) addresses on the edge router.
> # Ensure that if there is an active uplink, that uplink should have one 
> incoming link for every address for which there is at least one local 
> consumer.



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

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to