As a followup: We were looking over the release notes for AMQ 5.4
today, and a co-worker noticed https://issues.apache.org/activemq/browse/AMQ-2833
. This allows Stomp clients to indicate text vs byte messages via a
new custom Stomp header. This is perfect for our situation, and we're
loo
Hi Alex,
I think it's a bigger problem to pass and handle byte[] content in
JavaScript. All patches are welcomed, of course :)
Cheers
--
Dejan Bosanac - http://twitter.com/dejanb
Open Source Integration - http://fusesource.com/
ActiveMQ in Action - http://www.manning.com/snyder/
Blog - http://ww
On Jul 9, 2010, at 3:44 PM, Alex Dean wrote:
On Jul 9, 2010, at 1:50 PM, Alex Dean wrote:
I have a Ruby script which publishes a message to an ActiveMQ topic
via Stomp. I'm attempting to send these messages to the topic used
by the demo chat.html included in ActiveMQ, so I'm using the XM
On Jul 9, 2010, at 1:50 PM, Alex Dean wrote:
I have a Ruby script which publishes a message to an ActiveMQ topic
via Stomp. I'm attempting to send these messages to the topic used
by the demo chat.html included in ActiveMQ, so I'm using the XML
message format expected by that page. chat.
I have a Ruby script which publishes a message to an ActiveMQ topic
via Stomp. I'm attempting to send these messages to the topic used by
the demo chat.html included in ActiveMQ, so I'm using the XML message
format expected by that page. chat.html is this one : http://fisheye6.atlassian.com
