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

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

Commit 1622d0e608738da7b603b7e497bc3a8166325865 in qpid-proton's branch 
refs/heads/go1 from [~aconway]
[ https://git-wip-us.apache.org/repos/asf?p=qpid-proton.git;h=1622d0e ]

PROTON-1085: c++: clean up access to message properties, instructions and 
annotations.

- Use proton::value& as message::body() type.
- Create pn_message on demand for empty message.
- Use proton::scalar as basis for messsage_id and annotation_key
  - message_id restricted to be one of: uint64_t, amqp_uuid, amqp_binary or 
amqp_string.
  - annotation_key restricted to be on of: uint64_t or amqp_symbol.
- Decode and cache application properties, annotations and instructions on 
demand as std::map.
  - message::properties() returns std::map<std::string, scalar>&
  - message::instructions()/annotations() returns std::map<annotation_key, 
value>&


> c++ improve message interface and dynamic value handling
> --------------------------------------------------------
>
>                 Key: PROTON-1085
>                 URL: https://issues.apache.org/jira/browse/PROTON-1085
>             Project: Qpid Proton
>          Issue Type: Improvement
>          Components: cpp-binding
>    Affects Versions: 0.11.1
>            Reporter: Alan Conway
>            Assignee: Alan Conway
>             Fix For: 0.12.0
>
>
>     Improve body handling
>     Improve property maps
>     Improve handling of scalar values
>     Avoid returning opaque "data" from endpoint and message accessors



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to