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

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

Commit 771c9c9641a6e3b8180c2628d1192dca1ba92339 in qpid-dispatch's branch 
refs/heads/master from Ken Giusti
[ https://gitbox.apache.org/repos/asf?p=qpid-dispatch.git;h=771c9c9 ]

DISPATCH-1311: move qdr_delivery_t API to its own source files

This patch merely moves code and does some renaming of functions.  No
changes to actual functionality have occurred - it is simply a
reorganization of code layout.

This closes #489


> Move the qdr_delivery_t code to a dedicated file (reorganization)
> -----------------------------------------------------------------
>
>                 Key: DISPATCH-1311
>                 URL: https://issues.apache.org/jira/browse/DISPATCH-1311
>             Project: Qpid Dispatch
>          Issue Type: Sub-task
>          Components: Router Node
>    Affects Versions: 1.6.0
>            Reporter: Ken Giusti
>            Assignee: Ken Giusti
>            Priority: Major
>              Labels: delivery-refactor
>
> Let's start the process of moving delivery settlement and disposition 
> handling out of the core thread by isolating the qdr_delivery_t handling 
> code.  This code is currently residing in the transfer.c source file which 
> also contains various link and connection state handling.  The qdr_delivery_t 
> structure definition should also be moved out of the common router core 
> private header file.
> This change will simply move delivery code to its own delivery.c and 
> delivery.h in the router_core directory (for now).  No functional changes 
> will be made, though some method names may be changed for consistency.



--
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