Yes, that's what "Cross Language Clients and Protocols" means. "Cross Protocol" means that it's possible to communicate with an ActiveMQ broker via multiple different protocols (e.g. OpenWire, STOMP, REST) and the broker will automatically transmit messages using the protocol each individual client has chosen, even if it's not the protocol used by the producer of the message. "Cross Language" means that there are native libraries that support some or all of the protocols in a number of different languages, including Java, C++, and C#.
Tim On Tue, Mar 29, 2016 at 8:16 PM, William Greene <williamkgre...@gmail.com> wrote: > http://activemq.apache.org/rest.html > > Doesn't matter the producer > On Mar 29, 2016 9:02 PM, "bryanevil" <bryane...@hotmail.com> wrote: > > > Lets say I have an existing c++ want to stream messages (struct, binary > > stream, string, format really doesn't metter) to java world. Does > ActiveMQ > > provide c++ message producer and java message consumer that can bridge > > between these two world? Does the "Cross Language Clients and Protocols" > > stated at the ActiveMQ web front page implied that? > > > > > > > > > > -- > > View this message in context: > > > http://activemq.2283324.n4.nabble.com/What-is-Cross-Language-Clients-and-Protocols-means-tp4710044.html > > Sent from the ActiveMQ - User mailing list archive at Nabble.com. > > >
