[jira] [Updated] (PROTON-1288) c++ provide access to message maps as proton::value

["Robbie Gemmell (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/PROTON-1288?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Robbie Gemmell updated PROTON-1288:
-----------------------------------
    Affects Version/s: 0.15.0
        Fix Version/s:     (was: 0.15.0)
                       0.16.0

Unclear anything has been done for this so I'm removing the 0.15.0 fix-version, bumping to 0.16.0 as it looks to be under consideration already.

> c++ provide access to message maps as proton::value
> ---------------------------------------------------
>
>                 Key: PROTON-1288
>                 URL: https://issues.apache.org/jira/browse/PROTON-1288
>             Project: Qpid Proton
>          Issue Type: Bug
>          Components: cpp-binding
>    Affects Versions: 0.14.0, 0.15.0
>            Reporter: Alan Conway
>            Assignee: Alan Conway
>             Fix For: 0.16.0
>
>
> We need to provide access to the message property maps as a proton::value. 
> Given
> {code}
>     std::map<string, scalar> my_map;
>     proton::message m;
> {code}
> Here are some options:
> 1. Add new message accessor: proton::value& properties_value()
>    proton::get(m.properties_value(), my_map)
> 2. Add value() accessor to cached_map
>    proton::get(m.properties().value(), my_map)
> 3. Make cached_map : public proton::value()
>    proton::get(m.properties(), my_map)
> 3 is neatest, 1 provides a clearer separation between the case where you want a convenient cached map vs. you want to decode to your own C++ map, work on it, and possibly re-encode it later. I lean towards 3. but open to persuasion.



--
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