On 11/28/2013 06:33 AM, Robert Davies wrote:
There’s no reason that there aren’t other clients for OpenWire other than we
hadn’t got round to it (there’s been little demand for it as we’ve has STOMP -
so its not as if there hasn’t been at least some connectivity). As ActiveMQ now
supports AMQP 1.0 - it would make sense to utilise clients that support that -
I believe the QPid project have plans to extend the AMQP 1.0 beyond Java and
C/C++ to Python and Perl etc.
There are perl and python SWIG wrappers around the current Qpid c++
client, so you can use those to speak AMQP 1.0 to ActiveMQ if desired.
On 28 Nov 2013, at 06:03, xbhanu <xbh...@gmail.com> wrote:
Hi,
I was just curious to know that just like there is a Qpid provided AMQP
implementation for clients in Perl/Python/Java/C consistently,
Why doesnt ActiveMQ has a similar arrangement for OpenWire?
Why do we need to depend on STOMP for our Perl/Python use cases and then
stick to only text messages.?
(P.S I know about the tricky content-length and bytes message support)
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Query-regarding-OpenWire-STOMP-AMQP-tp4674898.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Rob Davies
-----------------
Red Hat, Inc
Twitter: rajdavies
Blog: http://rajdavies.blogspot.com
ActiveMQ in Action: http://www.manning.com/snyder/
