[
https://issues.apache.org/jira/browse/PROTON-2427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17438799#comment-17438799
]
ASF subversion and git services commented on PROTON-2427:
---------------------------------------------------------
Commit 7f3320d9941620e33f7553caccd22187474848ee in qpid-proton's branch
refs/heads/main from Andrew Stitcher
[ https://gitbox.apache.org/repos/asf?p=qpid-proton.git;h=7f3320d ]
PROTON-2456: Fix for error in PROTON-2427
> Avoid using pn_message_id()/pn_message_correlation_id() APIs in examples and
> bindings
> -------------------------------------------------------------------------------------
>
> Key: PROTON-2427
> URL: https://issues.apache.org/jira/browse/PROTON-2427
> Project: Qpid Proton
> Issue Type: Improvement
> Components: cpp-binding, proton-c
> Reporter: Andrew Stitcher
> Assignee: Andrew Stitcher
> Priority: Major
> Fix For: proton-c-0.36.0
>
>
> These APIs return a pn_data_t to represent a message id/correlation id which
> has a very restricted set of possible values. All of which are simple scalars
> - ulong, uuid, binary and string. There is already a setter/getter API that
> returns a pn_atom_t which is a much simpler and more efficient
> representation, so we should use this.
> We can make up the small API lack of pn_atom_t by introducing some
> pn_atom_put/get_ulong/uuid/string/binary APIs. But initially pn_atom_t is
> easy enough to construct/deconstruct especially with C99 structure
> initiialisers.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
