> > If we ever meet the first round is on me!
> >
> > Paul
> >
> > ________________
> > From: Steve Huston [shus...@riverace.com]
> > Sent: Tuesday, February 16, 2016 3:34 PM
> > To: users@qpid.apache.org
> > Subject
_
> From: Steve Huston [shus...@riverace.com]
> Sent: Tuesday, February 16, 2016 3:34 PM
> To: users@qpid.apache.org
> Subject: RE: QPID C++ broker and Java - One broker to "rule them all"
>
> Hi Paul,
>
>> -Original Message-
"rule them all"
Hi Paul,
> -Original Message-
> From: Flores, Paul A. [mailto:paul.a.flo...@saic.com]
> Sent: Tuesday, February 16, 2016 4:26 PM
> To: users@qpid.apache.org
> Subject: RE: QPID C++ broker and Java - One broker to "rule them all"
>
&
Hi Paul,
> -Original Message-
> From: Flores, Paul A. [mailto:paul.a.flo...@saic.com]
> Sent: Tuesday, February 16, 2016 4:26 PM
> To: users@qpid.apache.org
> Subject: RE: QPID C++ broker and Java - One broker to "rule them all"
>
> Steve,
>
> The c
QPID JMS utilizing
the C++ Broker (qpidd)?
Paul
From: Steve Huston [shus...@riverace.com]
Sent: Tuesday, February 16, 2016 3:07 PM
To: users@qpid.apache.org
Subject: RE: QPID C++ broker and Java - One broker to "rule them all"
There's
.flo...@saic.com]
> Sent: Tuesday, February 16, 2016 1:29 PM
> To: users@qpid.apache.org
> Subject: RE: QPID C++ broker and Java - One broker to "rule them all"
>
> Per Steve's advice:
>
> Environment:
> Centos 5.11 (moving soon to 7)
> C++: gcc 4.1.2
&
e.org
Subject: RE: QPID C++ broker and Java - One broker to "rule them all"
As long as the front end, back end, and broker can speak the same AMQP version,
they should all play nice regardless of the programming language.
If you can be a little more specific about the client code version
to do the
job.
-Steve
> -Original Message-
> From: Flores, Paul A. [mailto:paul.a.flo...@saic.com]
> Sent: Tuesday, February 16, 2016 1:06 PM
> To: users@qpid.apache.org
> Subject: QPID C++ broker and Java - One broker to "rule them all"
>
> Situation
Situation:
I am looking at a mixed language implementation.
Server side (backend) is in C++ while user facing side (frontend) is Java.
A fair amount of JNI "in play".
Specific option of using JMS would be painful because there is a substantial
amount of backend communications between s
