qpid-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Frank Quinn <fquinn...@gmail.com>
Subject Re: Alternatives to pn_messenger (QPID Proton C)
Date Wed, 03 May 2017 21:27:37 GMT
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.


On Wed, 3 May 2017, 21:58 Andrew Stitcher, <astitcher@apache.org> 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: users-unsubscribe@qpid.apache.org
> For additional commands, e-mail: users-help@qpid.apache.org

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message