Per Steve's advice: Environment: Centos 5.11 (moving soon to 7) C++: gcc 4.1.2 Java: 1.7.0_95
QPID Messaging API: qpid-cpp-0.34 C++ Broker ________________________________________ From: Steve Huston [shus...@riverace.com] Sent: Tuesday, February 16, 2016 12:13 PM To: users@qpid.apache.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 versions, it's highly likely that someone can help point you to at least one broker 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: > > > > 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 servers. > > > > Questions are straightforward. > > > > How do I get both sides (backend and frontend) to use the same Broker? > > > > Is JNI the only option? > > > > Insights and comments are welcomed and appreciated. > > > > Paul > > > > p.s. I apologize for the "Lord of the Rings" reference in subject line. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org For additional commands, e-mail: users-h...@qpid.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org For additional commands, e-mail: users-h...@qpid.apache.org
