On 05/21/2014 02:10 PM, Ken Giusti wrote:
I think of qpid::messaging as being a "traditional" client api.
[...]
Messenger, as an alternative, provides (or at least promises to
provide) solutions to a lot of the issues a "traditional" API has
left to the application implementation. Things like
Hi Gordon,
- Original Message -
> From: "Gordon Sim"
> To: us...@qpid.apache.org
> Cc: proton@qpid.apache.org
> Sent: Monday, May 19, 2014 11:25:41 AM
> Subject: Re: Client APIs and AMQP 1.0 (was Re: Using the messenger API to
> connect to a server with
On 05/15/2014 01:44 PM, Ken Giusti wrote:
I think we should develop Messenger as an alternative client API to
qpid::messaging, focusing on use cases that are not necessarily well
covered by the existing qpid::messaging API. I think they
complement each other nicely.
In what way do you think th
uot;
> To: us...@qpid.apache.org
> Cc: proton@qpid.apache.org
> Sent: Tuesday, May 13, 2014 9:48:15 AM
> Subject: Client APIs and AMQP 1.0 (was Re: Using the messenger API to connect
> to a server without sending or
> subscribing)
>
> On 04/28/2014 10:21 PM, Gordon Sim wrote
On 04/28/2014 10:21 PM, Gordon Sim wrote:
On 04/23/2014 05:17 PM, Fraser Adams wrote:
BTW I wouldn't want to come across as favouring proton Messenger or
qpid::messaging over the other, as I said previously they are peer APIs
with different advantages and disadvantages,
I'd certainly agree the
On 04/23/2014 05:17 PM, Fraser Adams wrote:
On 23/04/14 16:12, Rafael Schloming wrote:
On Wed, Apr 23, 2014 at 10:51 AM, Chris White wrote:
Our server backend is
built on
the qpid-proton library so ideally we would like our client API to
also be
built using qpid-proton library function.
As an
On Wed, 2014-04-23 at 17:17 +0100, Fraser Adams wrote:
> On 23/04/14 16:12, Rafael Schloming wrote:
> > On Wed, Apr 23, 2014 at 10:51 AM, Chris White1
> > wrote:
> >
> >> Hi all
> >>
> >> Thanks for the informative and very helpful responses.
> >>
> >> We did look at qpid:Messaging but this seems
On Wed, Apr 23, 2014 at 12:10 PM, Dominic Evans wrote:
> > My inclination would be to add some sort of policy or mode to messenger.
> > I'm not sure what I'd call it, but with this mode enabled, messenger
> (when
> > started) would always maintain active connections and/or links to any
> > declare
On 23/04/14 16:12, Rafael Schloming wrote:
On Wed, Apr 23, 2014 at 10:51 AM, Chris White1 wrote:
Hi all
Thanks for the informative and very helpful responses.
We did look at qpid:Messaging but this seems to be separate from the
qpid-proton library, and there is a concern that the is no Java A
Hursley Park, UK
--
View this message in context:
http://qpid.2158936.n2.nabble.com/Using-the-messenger-API-to-connect-to-a-server-without-sending-or-subscribing-tp7607184p7607280.html
Sent from the Apache Qpid Proton mailing list archive at Nabble.com.
On Wed, Apr 23, 2014 at 10:51 AM, Chris White1 wrote:
> Hi all
>
> Thanks for the informative and very helpful responses.
>
> We did look at qpid:Messaging but this seems to be separate from the
> qpid-proton library, and there is a concern that the is no Java API and
> some of the function we req
the messenger API to connect to a server without
sending or subscribing
Hi Chris,
Sorry for chiming in late, I've been in and out of meetings all day.
Comments are inline...
On Tue, Apr 22, 2014 at 2:49 AM, Chris White1
wrote:
> Hi
>
> I'm part of the IBM team developing MQ Light
Hi Chris,
Sorry for chiming in late, I've been in and out of meetings all day.
Comments are inline...
On Tue, Apr 22, 2014 at 2:49 AM, Chris White1 wrote:
> Hi
>
> I'm part of the IBM team developing MQ Light (
> https://www.ibmdw.net/messaging/mq-light/) and we are implementing our
> client API
On 22/04/14 19:27, dnwe wrote:
On 22/04/14 08:26, Fraser Adams wrote:
I'm sure others with more detailed knowledge of the background would be
able to give a better answer, but in short I think the thing that you
need to bear in mind is that proton Messenger is a *Message* oriented
API as opposed
Evans
WebSphere MQ - Development
IBM Software Group, Hursley Park, UK
--
View this message in context:
http://qpid.2158936.n2.nabble.com/Using-the-messenger-API-to-connect-to-a-server-without-sending-or-subscribing-tp7607184p7607249.html
Sent from the Apache Qpid Proton mailing list archive at Nabble.com.
undefined
undefined
I'm sure others with more detailed knowledge of the background would be
able to give a better answer, but in short I think the thing that you
need to bear in mind is that proton Messenger is a *Message* oriented
API as opposed to a *Connection* oriented API, so for example compare
the approach
Hi
I'm part of the IBM team developing MQ Light (
https://www.ibmdw.net/messaging/mq-light/) and we are implementing our
client API using the AMQP Messenger C API. Our client API has a connect
function, which is required to be invoked before sending or receiving
messages. The AMQP Messager C A
19 matches
Mail list logo
