You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Ken Giusti (JIRA)" <ji...@apache.org> on 2015/04/14 21:00:13 UTC
[jira] [Commented] (DISPATCH-135) Move the qd_delivery_t
functionality into the router node
[ https://issues.apache.org/jira/browse/DISPATCH-135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14494603#comment-14494603 ]
Ken Giusti commented on DISPATCH-135:
-------------------------------------
Fixing DISPATCH-44 will require adding yet more state to the delivery objects. I'd prefer not to do that.
> Move the qd_delivery_t functionality into the router node
> ---------------------------------------------------------
>
> Key: DISPATCH-135
> URL: https://issues.apache.org/jira/browse/DISPATCH-135
> Project: Qpid Dispatch
> Issue Type: Improvement
> Components: Router Node
> Affects Versions: 0.4
> Reporter: Ken Giusti
> Assignee: Ken Giusti
> Fix For: 0.5
>
>
> The current definition of the qd_delivery_t structure contains mostly router-specific members although it is defined as part of the container layer. Since it contains router data, it becomes necessary to have the container delivery APIs require holding the router lock.
> This structure should not be part of the generic container library. It should be moved into the router node (and renamed qd_router_delivery_t).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org