Using the amq-msg-type for Stomp->ActiveMQ messages from Ruby and
ActiveMQ<->Ajax to the Browser with amq.js and prototype,js
Had no problems when I did not use the header and we connected the Browser
via Orbited.
Ruby code:
javascript = render_to_string :update do |page|
page.insert_html :bottom,
"chat_message_list_#{params[:id]}", chat_message.to_html
page << "$('chat_window_#{params[:id]}_body').scrollTop =
$('chat_window_#{params[:id]}_body').scrollHeight;"
end
Orbited.send_data("CHANNEL_#{chat_message.window.workbench_id}", javascript)
Now we get 3 messages back from ActiveMQ for this single message. All this
JS has to be in one block to be run in the browser. Looking to change this
behavior back, or find a way to link these back together.
Looking thru the messages now.........
Phil
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Question-about-ajax-html-examples-on-website-tp3216811p3235218.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
