Hallo Rafael,

*HUGE* thanks!

30.01.2015 19:59, Rafael Schloming пишет:
> Hi Michael,
> 
> I just pushed some documentation for pn_data_t into the source tree. You
> can build the docs from source if you like. They will most likely apply to
> whatever version you are using as that API hasn't changed in a while. You
> can also just read the header file[1] directly, although it is less pretty.
> 
> [1]
> https://github.com/apache/qpid-proton/blob/master/proton-c/include/proton/codec.h
> 
> The 0.9 release will be happening soon, and the website docs will be
> updated when that happens.
> 
> --Rafael
> 
> On Fri, Jan 30, 2015 at 5:35 AM, Michael Ivanov <[email protected]> wrote:
> 
>> Greetings!
>>
>> I want to port some c++ messaging code from qpid cpp messanger to proton.
>> How one is supposed to perform data serialization/deserialization here?
>> In cpp messenger I used encode/decode functionality and then copied the
>> actual data between map and user object. What should I use in proton?
>> As far as I could discover from proton C API reference I need to use
>> pn_data_t to get the data from pn_message_t, but regrettably reference
>> just lists all pn_data_t handling functions without even summarizing
>> their meaning :-/ Is there a description on the subject or examples
>> that I can use as a starting point?
>>
>> Best regards,
>> --
>>  \   / |                                   |
>>  (OvO) |  Mikhail Iwanow                   |
>>  (^^^) |      Voice:   +7 (911) 223-1300   |
>>   \^/  |      E-mail:  [email protected]   |
>>   ^ ^  |                                   |
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [email protected]
>> For additional commands, e-mail: [email protected]
>>
>>
> 


-- 
 \   / |                                   |
 (OvO) |  Михаил Иванов                    |
 (^^^) |      Тел.:    +7(911) 223-1300    |
  \^/  |      E-mail:  [email protected]   |
  ^ ^  |                                   |

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to