Thanks Andrew, Our application distinguishes between transport and payload. We have a *lot* of code around the payload which happily works with pn_message_t which would be extremely painful to port to the C++ API. We then use pn_messenger purely for transport send / recv.
Cheers, Frank On Wed, 3 May 2017, 21:58 Andrew Stitcher, <[email protected]> wrote: > On Wed, 2017-05-03 at 20:48 +0000, Frank Quinn wrote: > > ... > > We also make heavy use of pn_message_t which I thought might have > > been a > > possible overload for the c++ proton::message constructor but I can't > > see > > one unless there are conversion functions somewhere public? > > The C++ API is intended to be used by itself, and not in conjunction > with the C API at the same time. > > Having said that proton::message is only a wrapper for pn_message_t. > But if you are using the API there's no string reason to ever use the C > pn_message_t API. > > What are you doing the uses the pn_message_t API that is separate from > sending messages, that can't be done solely in C++? > > You should be able to everything more easily just using the C++ API. If > not, then we'll seriously look at what you are doing that can't be > done, as we do want the API to cover a wide swath. > > Andrew > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
