Mailing-List: contact users-help@qpid.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@qpid.apache.org
DMARC-Filter: OpenDMARC Filter v1.3.2 mx1.redhat.com AB5AB4E34D
Message-ID: <1493845113.5473.8.camel@apache.org>
Subject: Re: Alternatives to pn_messenger (QPID Proton C)
From: Andrew Stitcher <astitcher@apache.org>
To: users@qpid.apache.org
Date: Wed, 03 May 2017 16:58:33 -0400
In-Reply-To: <CAL75PSeKSDS-fFgh+T5yh=f2ZC3szH2QVfcbuhptd+eXNYAfZQ@mail.gmail.com>
References: 
	<CAL75PSdAAurv+Rq+22kZLV3rBvcf_WRHxmfKVSXa53-OCtyV1Q@mail.gmail.com>
	 <CAFitrpRmHtnQuTVPe2o7=CcvisFdxiG1p4uy+qBq0K=tVQ9X4Q@mail.gmail.com>
	 <1493840605.5473.6.camel@apache.org>
	 <CAL75PSeKSDS-fFgh+T5yh=f2ZC3szH2QVfcbuhptd+eXNYAfZQ@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
archived-at: Wed, 03 May 2017 20:58:39 -0000

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