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

ASF subversion and git services commented on PROTON-2451:
---------------------------------------------------------

Commit 7a641e8a6eb95f0be9e9b74f70a71eeeced40391 in qpid-proton's branch 
refs/heads/main from Andrew Stitcher
[ https://gitbox.apache.org/repos/asf?p=qpid-proton.git;h=7a641e8 ]

PROTON-2451: Fix tests that 'know' exactly what frame it is expecting back

The current version of the generated code is a little different from
the previous code and generates more compact encodings in a few different
places.


> Reduce (ultimately eliminate) all use of the pn_data_t data structure in AMQP 
> frame processing
> ----------------------------------------------------------------------------------------------
>
>                 Key: PROTON-2451
>                 URL: https://issues.apache.org/jira/browse/PROTON-2451
>             Project: Qpid Proton
>          Issue Type: Improvement
>          Components: proton-c
>            Reporter: Andrew Stitcher
>            Assignee: Andrew Stitcher
>            Priority: Major
>             Fix For: proton-c-0.37.0
>
>
> In current proton protocol processing code make heavy use of the pn_data_t 
> data structure for coding and decoding AMQP frames to send and receive. 
> Unfortunately the data structure is complex and the code which uses it is not 
> very efficient. This means that a lot of CPU is consumed maniputing these 
> data structures unnecessarily during the critical path operations of proton. 
> During frame processing pn_data_t is not even really necessary as it is only 
> used as an intermediary to extract necessary frame parameters out of the 
> frames (or as an intermediary to construct the frames from the necessary 
> frame parameters.
> This means that is entirely feasible to go directly from/to the parameters 
> to/from the frames without using an intermediate pn_data_t at all.
> The most complicated aspect of this and one which will be deferred somewhat 
> is that of using non scalar structured data as part of AMQP frames.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

Reply via email to