Thanks Alan.
On Thu, Mar 24, 2016 at 11:02 PM, Alan Conway wrote:
> On Fri, 2016-03-18 at 16:01 +0100, Mark Banner wrote:
> > I have gone through the documentation and code and have the following
> > understanding of container vs connection_engine:
> >
> > Container is an adapter for pn_reactor.
On Fri, 2016-03-18 at 16:01 +0100, Mark Banner wrote:
> I have gone through the documentation and code and have the following
> understanding of container vs connection_engine:
>
> Container is an adapter for pn_reactor. The proton reactor manages
> network
> IO and sends events to a registered ha
On Thu, 2016-03-17 at 20:02 +0100, Mark Banner wrote:
> Hi,
>
> I am creating an application which is using the C++ API for AMQP
> (0.12) and
> I am trying to wrap my head around how to create a sender when I have
> a new
> message to send.
>
> For receiving messages, I can create a receiver when
Hi,
I am creating an application which is using the C++ API for AMQP (0.12) and
I am trying to wrap my head around how to create a sender when I have a new
message to send.
For receiving messages, I can create a receiver when the container is
finished initializing and on_message will be called wh
I'll look into the connection_engine API then. Thanks for the reply!
On Thu, Mar 17, 2016 at 9:15 PM, Alan Conway wrote:
> On Thu, 2016-03-17 at 20:02 +0100, Mark Banner wrote:
> > Hi,
> >
> > I am creating an application which is using the C++ API for AMQP
> > (0.12) and
> > I am trying to wrap
I have gone through the documentation and code and have the following
understanding of container vs connection_engine:
Container is an adapter for pn_reactor. The proton reactor manages network
IO and sends events to a registered handler so container registers an proxy
handler which will pass even