<div class="im">2011/8/4 sid__ <span dir="ltr"><<a href="mailto:sid.ravichandran@gmail.com" target="_blank">sid.ravichandran@gmail.com</a>></span><br></div><div class="gmail_quote"><div class="im"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div>I am unable to figure how one would go about doing this. Since they<br>
run on separate ports there would be the issue of violating the same<br>
origin policy.<br>
<br>
I am familiar with how Orbited provides long polling support for XMPP<br>
but I was unable to find something similar for AMQP. But how would the<br>
AMQP server respond without and explicit HTTP Request handler.<br>
<br>
I would really appreciate some help on how this should be implemented.<br>
Some sample code would be great.<br>
<br></div></blockquote></div><div><br>You can combined multiple
EventMachine-based servers in the same process. You can combine
em-websocket, amqp gem and something that helps you with long polling
(it probably can be something Thin or Goliath-based).<br>
</div><div class="im"><blockquote class="gmail_quote" style="margin:0pt 0pt 0pt 0.8ex;border-left:1px solid rgb(204, 204, 204);padding-left:1ex"><div>
Also I would like to know if the general practice is to run the AMQP<br>
server as daemon or as part of Rails app.</div></blockquote></div></div><br>I typically recommend running amqp daemons as satellite applications but there are certainly cases when people run amqp daemons<br>basically
embedded into Web applications. Just keep in mind Ruby
1.8.7 threading scheduler is not really fair (some threads may be given
significantly more time to run than others) and while 1.9.2 uses kernel
threads that are a lot better in this regard, I have seen obscure 1.9.2 VM crashes with multithreaded applications.<br clear="all"><br>-- <br>MK<br><br><a href="http://github.com/michaelklishin" target="_blank">http://github.com/michaelklishin</a><br>
<a href="http://twitter.com/michaelklishin" target="_blank">http://twitter.com/michaelklishin</a><br><br>