<br><br><div class="gmail_quote">2012/10/28 Mark <span dir="ltr"><<a href="mailto:static.void.dev@gmail.com" target="_blank">static.void.dev@gmail.com</a>></span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div style="word-wrap:break-word">Is this the case? Is the async AMQP gem recommend in production Unicorn environments?<div><div><br></div></div></div></blockquote><div><br></div><div>You can use either but Bunny has limitations, performs poorly and needs a ground-up rewrite.</div>
<div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word"><div><div></div><div>Another question regarding the documentation on connecting to Unicorn: <a href="http://rubyamqp.info/articles/connecting_to_broker/#using_ruby_amqp_gem_with_unicorn" target="_blank">http://rubyamqp.info/articles/connecting_to_broker/#using_ruby_amqp_gem_with_unicorn</a> How come it doesn't include the use of: AMQP::Utilities::EventLoopHelper.run or AMQP::Integration::Rails.start? I understand that a new thread must be created in the after_fork but is the AMQP::Integration::Rails.start necessary or can/should that be used in any controller/action where we intend to use AMQP? </div>
</div></div></blockquote></div><br>The docs were written before EventLoopHelper was added. And no, you should not go through the whole<div>connection process on every action. Do it once on boot.<br clear="all"><div><br></div>
-- <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>
</div>