You are viewing a plain text version of this content. The canonical link for it is here.
Posted to proton@qpid.apache.org by "Andrew Stitcher (JIRA)" <ji...@apache.org> on 2014/12/12 21:46:13 UTC
[jira] [Resolved] (PROTON-770) Refactor Proton C to eliminate the
pn_dispatcher_t class
[ https://issues.apache.org/jira/browse/PROTON-770?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andrew Stitcher resolved PROTON-770.
------------------------------------
Resolution: Fixed
Fix Version/s: 0.9
> Refactor Proton C to eliminate the pn_dispatcher_t class
> --------------------------------------------------------
>
> Key: PROTON-770
> URL: https://issues.apache.org/jira/browse/PROTON-770
> Project: Qpid Proton
> Issue Type: Improvement
> Reporter: Andrew Stitcher
> Assignee: Andrew Stitcher
> Fix For: 0.9
>
>
> The pn_dispatcher_t class has two intertwined purposes -
> * To hold some temporary and scratch data used for processing incoming and outgoing frames.
> * To dispatch incoming frames to frame handling code.
> It turns out that the first purpose is overhead: The temporary data can be better passed as parameters to the code that is using it; The scratch data is duplicated and would be better put in the associated pn_transport_t which is where is ends up going anyway.
> The second purpose turns out to boil down to 1 boolean and some code which can be handled differently. The boolean is to tell the dispatcher to stop.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)