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

ASF subversion and git services commented on QPID-5045:
-------------------------------------------------------

Commit 1526694 from [~tedross] in branch 'qpid/trunk'
[ https://svn.apache.org/r1526694 ]

QPID-5173
QPID-5045
QPID-5181
 - Major refactor of the routing data structure in preparation for multi-router 
operation.
 - Fixed the CMake bug in QPID-5173
 - Added Dynamic assignment of routable addresses for outbound links (QPID-5181)
 - Changed the indentation of the Python code from 2 spaces to 4 spaces.
 - Reduced the default log level to make the console less chatty.
                
> Dispatch - Refactor the router data structures to allow both message-based 
> and link-based routing that supports full link protocol
> ----------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: QPID-5045
>                 URL: https://issues.apache.org/jira/browse/QPID-5045
>             Project: Qpid
>          Issue Type: Improvement
>          Components: Qpid Dispatch
>            Reporter: Ted Ross
>            Assignee: Ted Ross
>
> Dispatch router supports two flavors of routing:
>  - Message Routing is performed using the "to" field and uses linked delivery 
> records to track disposition and settlement.
>  - Link Routing is performed using the target/source of an attach frame and 
> creates "virtual circuits" of linked-links to carry messages across a network.
> This Jira tracks changes to the router data structures to support these 
> routing features.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

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

Reply via email to