amqp 0.8.0.rc2 → 0.8.0.rc3

data/.gitignore

@@ -8,8 +8,7 @@
 Gemfile.lock
 
 spec/amqp.yml
-vendor/bundle
-vendor/cache
+vendor
 
 .yardoc/*
-doc/*
+doc/*

data/.travis.yml

@@ -1,7 +1,10 @@
-script: "bundle exec rspec spec"
+script: "bundle exec rake spec:ci"
 rvm:
   - 1.8.7
   - 1.9.2
   - ree
   - rbx
-  - jruby
+  - jruby
+gemfile:
+  - Gemfile
+  - gemfiles/eventmachine-pre

data/.yardopts

@@ -1,6 +1,8 @@
 --no-private
 --protected
 --markup="textile" lib/**/*.rb
+--main README.textile
 -
 LICENSE
+CHANGELOG
 docs/*.textile

data/CHANGELOG

@@ -1,35 +1,32 @@
 = Version 0.8.0
 
-  * [API] AMQP::Exchange#initialize now accepts :arguments option that takes a hash. Brokers
-          may implement AMQP extensions using (usually x-prefixed) declaration arguments.
-  * [API] AMQP::Queue#initialize now accepts :arguments option that takes a hash. RabbitMQ
-          recognizes x-message-ttl argument and uses it as message TTL in milliseconds for
-	  queue that is being declared.
+  * [FEATURE] AMQP 0.9.1 support, including tx.* operations class.
+  * [API] AMQP::Channel#initialize now takes 3rd (optional) options hash.
+  * [API] Broker connection class is now AMQP::Session.
+  * [API] AMQP::Error instance now may carry cause, an exception that caused exception in question to be raised.
+  * [API] When initial TCP connection fails, default action is now to raise AMQP::TCPConnectionFailed.
+  * [API] AMQP::BasicClient#reconnect now takes 2nd optional argument, period of waiting in seconds.
+  * [FEATURE] Handlers for initial connection failre, connection loss; channel-level exceptions handlers on Channel instances.
+  * [API] AMQP::Exchange#initialize now accepts :arguments option that takes a hash.
+  * [API] AMQP::Queue#initialize now accepts :arguments option that takes a hash.
   * [API] AMQP#Logger is deprecated. It will be removed before 1.0 release.
   * [API] AMQP#fork is deprecated. It will be removed before 1.0 release.
   * [API] AMQP::RPC is deprecated. It will be removed before 1.0 release.
-  * [FEATURE] Significant improvements to the documentation
+  * [FEATURE] Significant improvements to the documentation. From now on lack of/poor documentation is considered a severe bug.
   * [FEATURE] Support for RabbitMQ extensions to AMQP 0.9.1
-  * [API] AMQP::Exchange#publish now accepts (an optional) block that is called as soon as message
-          is considered published (EventMachine loop has pushed payload down the network stack).
-  * [API] AMQP::Channel.new now accepts (an optional) block and yields newly opened channel to it as soon as
-          channel.open-ok arrives from the broker.
+  * [API] AMQP::Exchange#publish now accepts (an optional) callback.
+  * [API] AMQP::Channel.new now accepts (an optional) callback.
   * [API] AMQP::Header#ack now can acknowledge multiple deliveries
   * [API] AMQP::Exchange#delete now takes (an optional) block that is called when exchange.delete-ok response arrives.
   * [API] AMQP::Header now implements #to_hash
   * [API] AMQP::Queue#pop block now can take 1, 2 or 3 arguments.
-          1 argument means handler is only interested in content payload
-	  2 arguments mean handler is interested in headers and the content
-	  3 arguments mean handler is interested in headers, content and AMQP method instance
   * [API] AMQP::Queue#purge  now takes an optional block which is called when queue.purge-ok response arrives.
   * [API] AMQP::Queue#delete now takes an optional block which is called when queue.delete-ok response arrives.
   * [API] AMQP::Queue#delete now accepts :nowait option.
   * [API] AMQP::Queue#unbind now takes an optional block which is called when queue.unbind-ok response arrives.
   * [API] AMQP::Queue#unbind now accepts :routing_key as alias to :key. we believe it is a good idea to use AMQP terms.
-  * [API] AMQP::Channel#prefetch now takes (an optional) 2nd parameter that specifies
-          that QoS settings should be applied to underlying connection, as well as optional callback.
-  * [API] AMQP::Channel#recover now takes (an optional) callback that is called when
-          basic.recover-ok is received.
+  * [API] AMQP::Channel#prefetch now takes (an optional) 2nd parameter that specifies that QoS settings should be applied to underlying connection, as well as optional callback.
+  * [API] AMQP::Channel#recover now takes (an optional) callback that is called when basic.recover-ok is received.
   * [API] AMQP::Frame is gone.
   * [API] AMQP::Buffer is gone. Serialization & framing are now handled primarily by amq-protocol.
   * [FEATURE] AMQP gem is now AMQP 0.9.1 compatible: it runs atop of amq-client gem
@@ -40,11 +37,11 @@
 
   * [BUG] AMQP gem no longer conflicts with Builder 2.1.2 on Ruby 1.9.
         All Ruby on Rails 3 users who run Ruby 1.9 are highly recommended
-  			to upgrade!
+                        to upgrade!
   * [API] AMQP::Exchange.default no longer caches exchange object between calls
           because it may lead to very obscure issues when channel that exchange was
-	  using is closed (due to connection loss, as part of test suite teardown
-	  or in any other way).
+          using is closed (due to connection loss, as part of test suite teardown
+          or in any other way).
 
   * [API] AMQP::Exchange.default now accepts channel as a parameter.
   * [API] AMQP::Exchange#channel

data/Gemfile

@@ -1,18 +1,19 @@
 # encoding: utf-8
 
-source "http://gemcutter.org"
+source :rubygems
 
 # Use local clones if possible.
+# If you want to use your local copy, just symlink it to vendor.
 def custom_gem(name, options = Hash.new)
-  local_path = File.expand_path("../../#{name}", __FILE__)
-  if ENV["USE_AMQP_CUSTOM_GEMS"] && File.directory?(local_path)
+  local_path = File.expand_path("../vendor/#{name}", __FILE__)
+  if File.exist?(local_path)
     gem name, options.merge(:path => local_path).delete_if { |key, _| [:git, :branch].include?(key) }
   else
     gem name, options
   end
 end
 
-gem "eventmachine"
+custom_gem "eventmachine"
 gem "json", :platform => :ruby_18
 custom_gem "amq-client",   :git => "git://github.com/ruby-amqp/amq-client.git",   :branch => "master"
 custom_gem "amq-protocol", :git => "git://github.com/ruby-amqp/amq-protocol.git", :branch => "master"
@@ -27,6 +28,7 @@ group(:development) do
 end
 
 group(:test) do
-  gem "rspec", ">=2.0.0"
+  gem "rspec", ">=2.5.0"
+  gem "rake"
   custom_gem "evented-spec", :git => "git://github.com/ruby-amqp/evented-spec.git", :branch => "master"
 end

data/README.textile

@@ -1,11 +1,16 @@
 h1. About amqp gem "!http://travis-ci.org/ruby-amqp/amqp.png!":http://travis-ci.org/ruby-amqp/amqp
 
-amqp gem is a widely used, feature-rich asynchronous Ruby AMQP client built on top of "EventMachine":http://rubyeventmachine.com.
+amqp gem is a widely used, feature-rich, well-maintained asynchronous AMQP 0.9.1 client with batteries included.
 This library works with Ruby 1.8.7, Ruby 1.9.2, JRuby, REE and Rubinius, and is
 licensed under the "Ruby License":http://www.ruby-lang.org/en/LICENSE.txt.
 Versions 0.8.0 and later of amqp gem implement "AMQP 0.9.1":http://bit.ly/hw2ELX.
 
 
+h2. I know what AMQP is, how do I get started?
+
+See "Getting started with amqp gem" and "Documentation: tutorials, guides & API reference" sections below.
+
+
 h2. What is AMQP?
 
 AMQP is an "open standard for messaging middleware":http://www.amqp.org/confluence/display/AMQP/About+AMQP that
@@ -32,7 +37,7 @@ Specific examples:
    there are some new results.
 
  * Content aggregators may update full-text search and geospatial search indexes
-	 by delegating actual indexing work to other applications over AMQP.
+         by delegating actual indexing work to other applications over AMQP.
 
  * Companies may provide "Firehose-like" push APIs to their customers, partners
    or just general public.
@@ -42,11 +47,11 @@ Specific examples:
 
  * An application that watches updates from a real-time stream (be it markets data
    or Twitter stream) can propagate updates to interested parties, including
-	 Web applications that display that information in the real time.
+         Web applications that display that information in the real time.
 
 
 
-h2. Getting started with amqp gem
+h2(Getting_started_with_amqp_gem). Getting started with amqp gem
 
 h3. Install RabbitMQ
 
@@ -62,37 +67,77 @@ h3. Install the gem
 
 h3. "Hello, World" example
 
-<pre>
+<pre><code>
 #!/usr/bin/env ruby
 # encoding: utf-8
 
 require "rubygems"
+# or
+#
+# require "bundler"
+# Bundler.setup
+#
+# if you use Bundler
+
 require 'amqp'
 
 EventMachine.run do
-  AMQP.connect(:host => 'localhost') do |connection|
-    puts "Connected to AMQP broker"
+  connection = AMQP.connect(:host => '127.0.0.1')
+  puts "Connected to AMQP broker. Running #{AMQP::VERSION} version of the gem..."
 
-    channel  = AMQP::Channel.new(connection)
-    queue    = channel.queue("amqpgem.examples.hello_world")
-    exchange = channel.default_exchange
+  channel  = AMQP::Channel.new(connection)
+  queue    = channel.queue("amqpgem.examples.hello_world", :auto_delete => true)
+  exchange = channel.direct("")
 
-    queue.subscribe do |payload|
-      puts "Received a message: #{payload}. Disconnecting..."
+  queue.subscribe do |payload|
+    puts "Received a message: #{payload}. Disconnecting..."
 
-      connection.close {
-        EM.stop { exit }
-      }
-    end
+    connection.close {
+      EM.stop { exit }
+    }
+  end
 
-    exchange.publish "Hello, world!", :routing_key => queue.name
-  end  
+  exchange.publish "Hello, world!", :routing_key => queue.name
 end
-</pre>
+</code></pre>
 
 (see "as a Gist":https://gist.github.com/910211)
 
 
+
+h2(#Documentation_tutorials_guides_API_reference). Documentation: tutorials, guides & API reference
+
+We believe that in order to be the best Ruby AMQP client out there, we need to care about documentation as much as
+code readability, API beauty and autotomated testing across 5 Ruby implementations on 3 operating systems.
+
+
+h3. Tutorials
+
+We have written and maintain "Getting started guide":http://rdoc.info/github/ruby-amqp/amqp/master/file/docs/GettingStarted.textile that is written in form of a tutorial.
+Check it out! If something isn't clear, every guide explains how to contact documentation authors.
+
+
+h3. Examples
+
+You can find many examples (both real-world cases and simple demonstrations)
+under "examples directory":https://github.com/ruby-amqp/amqp/tree/master/examples in the repository.
+Note that those examples are written against version 0.8.0.rc1 and later. 0.6.x and 0.7.x
+may not support certain AMQP protocol or "DSL syntax" features.
+
+
+h3. Guides
+
+"Documentation guides":http://rdoc.info/github/ruby-amqp/amqp/master/file/docs/DocumentationGuidesIndex.textile describe
+the library itself as well as AMQP usage scenarios, routing, error handing & recovery, broker-specific extensions, TLS support  and so on.
+
+
+h3. API reference
+
+"Reference documentation":http://rdoc.info/github/ruby-amqp/amqp/master/frames is up on rdoc.info and is updated daily.
+
+*If you don't find your answer in documentation, we consider it a high severity bug* that you should "file to us":http://github.com/ruby-amqp/amqp/issues.
+
+
 h2. How to use AMQP gem with Ruby on Rails, Merb, Sinatra and other web frameworks
 
 To use AMQP gem from web applications, you would need to have EventMachine reactor running.
@@ -141,13 +186,6 @@ gem "amqp", :git => "git://github.com/ruby-amqp/amqp.git", :branch => "master"
 
 
 
-h2. Examples
-
-You can find many examples (both real-world cases and simple demonstrations)
-under "examples directory":https://github.com/ruby-amqp/amqp/tree/master/examples in the repository.
-
-
-
 h2. How does amqp gem relate to amq-client gem, amq-protocol and libraries like bunny?
 
 See "this page about AMQP gems family":https://github.com/ruby-amqp/amq-client/blob/master/README.textile
@@ -209,7 +247,7 @@ use version 0.7.
 
 h2. Links
 
-* "API Documentation":http://rdoc.info/github/ruby-amqp/amq-protocol/master/frames
+* "API reference":http://rdoc.info/github/ruby-amqp/amqp/master/frames
 * "Examples":https://github.com/ruby-amqp/amq-protocol/tree/master/examples/
-* "Issue tracker":http://github.com/ruby-amqp/amq-protocol/issues
-* "Continous integration server":http://travis-ci.org/#!/ruby-amqp/amqp
+* "Issue tracker":http://github.com/ruby-amqp/amqp/issues
+* "Continous integration server":http://travis-ci.org/#!/ruby-amqp/amqp

data/Rakefile

@@ -1,8 +1,14 @@
+require 'fileutils'
 require 'rspec/core/rake_task'
 
 desc "Run spec suite (uses Rspec2)"
 RSpec::Core::RakeTask.new(:spec) { |t|}
 
+namespace :spec do
+  desc "Clean up rbx compiled files and run spec suite"
+  RSpec::Core::RakeTask.new(:ci) { |t| Dir.glob("**/*.rbc").each {|f| FileUtils.rm_f(f) } }
+end
+
 desc "Run specs with RCov"
 RSpec::Core::RakeTask.new(:rcov) do |t|
   t.rcov = true

data/amqp.gemspec

@@ -10,22 +10,22 @@ Gem::Specification.new do |s|
   s.authors = ["Aman Gupta", "Jakub Stastny aka botanicus", "Michael S. Klishin"]
   s.homepage = "http://github.com/ruby-amqp/amqp"
   s.summary = "AMQP client implementation in Ruby/EventMachine."
-  s.description = "Asynchronous AMQP 0.9.1 client for Ruby. Built on top of Eventmachine."
+  s.description = "Widely used, feature-rich asynchronous AMQP 0.9.1 client with batteries included"
   s.cert_chain = nil
   s.email = ["bWljaGFlbEBub3ZlbWJlcmFpbi5jb20=\n", "c3Rhc3RueUAxMDFpZGVhcy5jeg==\n"].map { |i| Base64.decode64(i) }
 
   # files
-  s.files = `git ls-files`.split("\n").reject { |file| file =~ /^vendor\// }
+  s.files = `git ls-files`.split("\n").reject { |file| file =~ /^vendor\// || file =~ /^gemfiles\// }
   s.require_paths = ["lib"]
 
   # RDoc
   s.has_rdoc = true
   s.rdoc_options = '--include=examples --main README.textile'
-  s.extra_rdoc_files = ["README.textile"] + Dir.glob("doc/*")
+  s.extra_rdoc_files = ["README.textile"] + Dir.glob("docs/*")
 
   # Dependencies
-  s.add_dependency "eventmachine", "~> 0.12.10"
-  s.add_dependency "amq-client", ">= 0.7.0.alpha2"
+  s.add_dependency "eventmachine"
+  s.add_dependency "amq-client", ">= 0.7.0.alpha13"
 
   begin
     require "changelog"

data/docs/08Migration.textile

@@ -0,0 +1,27 @@
+h1. TBD
+
+
+h2. About this guide
+
+TBD
+
+
+h2. Covered versions
+
+This guide covers amqp gem v0.8.0 and later.
+
+
+
+h2. TBD
+
+TBD
+
+
+
+h2. Tell us what you think!
+
+Please take a moment and tell us what you think about this guide on "Ruby AMQP mailing list":http://groups.google.com/group/ruby-amqp:
+what was unclear? what wasn't covered? maybe you don't like guide style or grammar and spelling are incorrect? Readers feedback is
+key to making documentation better.
+
+If mailing list communication is not an option for you for some reason, you can "contact guides author directly":mailto:michael@novemberain.com?subject=amqp%20gem%20documentation

data/docs/Bindings.textile

@@ -0,0 +1,27 @@
+h1. TBD
+
+
+h2. About this guide
+
+TBD
+
+
+h2. Covered versions
+
+This guide covers amqp gem v0.8.0 and later.
+
+
+
+h2. TBD
+
+TBD
+
+
+
+h2. Tell us what you think!
+
+Please take a moment and tell us what you think about this guide on "Ruby AMQP mailing list":http://groups.google.com/group/ruby-amqp:
+what was unclear? what wasn't covered? maybe you don't like guide style or grammar and spelling are incorrect? Readers feedback is
+key to making documentation better.
+
+If mailing list communication is not an option for you for some reason, you can "contact guides author directly":mailto:michael@novemberain.com?subject=amqp%20gem%20documentation

data/docs/ConnectingToTheBroker.textile

@@ -0,0 +1,277 @@
+h1. Connecting to the broker
+
+
+h2. About this guide
+
+This guide covers connection to AMQP broker from standalone and Web applications,
+connection error handling, authentication failure handling and related issues..
+
+
+h2. Covered versions
+
+This guide covers amqp gem v0.8.0 and later.
+
+
+
+h2. Terminology
+
+In this guide we define standalone application as application that does not run on
+a Web server like Unicorn or Passenger. The key difference is that these applications
+control main Ruby VM thread and often use it to run EventMachine event loop. When
+amqp gem is used inside of a Web applications, main thread is occupied by Web application
+server and code required to establish connection to AMQP broker needs to be a little
+bit different.
+
+
+
+h2. In standalone applications
+
+h3. EventMachine event loop
+
+amqp gem uses "EventMachine":http://rubyeventmachine.com under the hood and needs EventMachine
+event loop to be running in order to connect to AMQP broker or send any data. This means that
+before connecting to AMQP broker, we need to _start EventMachine reactor_ (get the event loop
+going). Here is how to do it:
+
+<pre>
+<code>
+require "amqp"
+
+EventMachine.run do
+  # ...
+end
+</code>
+</pre>
+
+"EventMachine.run":http://eventmachine.rubyforge.org/EventMachine.html#M000461 will block current thread until event loop is stopped.
+Standalone applications often can afford starting event loop on the main thread. If you have no experience with threading, this is a
+recommended way.
+
+
+h3. AMQP.connect with a block
+
+Once event loop is running, {AMQP.connect} method will attempt to connect to the broker. It can be used in two ways. Here is the
+first one:
+
+<pre>
+<code>
+require "amqp"
+
+EventMachine.run do
+  # using AMQP.connect with a block
+  AMQP.connect(:host => "localhost") do |client|
+    # connection is open and ready to be used
+  end
+end
+</code>
+</pre>
+
+{AMQP.connect} takes a block that will be executed as soon as AMQP connection is open (TCP connection was set up,
+authentication succeeded, broker and client finished negotiating connection parameters like max frame size).
+
+
+h3. AMQP.connect without a callback
+
+Alternative way of connecting is this:
+
+<pre>
+<code>
+require "amqp"
+
+EventMachine.run do
+  # using AMQP.connect with a block
+  client = AMQP.connect(:host => "hub.megacorp.internal", :username => "hedgehog", :password => "t0ps3kr3t")
+  # connection is not yet open, however, amqp gem will delay
+  # channel operations until after connection is open. However,
+  # amqp gem cannot solve every possible race condition so be careful
+end
+</code>
+</pre>
+
+If you do not need to assign returned value to a variable, "block version" is recommended because it eliminates issues that may
+arise from attempts to use a connection object that is not fully opened yet. For example, handling of authentication failures is simpler
+with the block version, as we will see in the following sections.
+
+
+h3. AMQP.start
+
+EventMachine.run and {AMQP.connect} with a block is such a common combination that amqp gem provides a shortcut:
+
+<pre>
+<code>
+require "amqp"
+
+AMQP.start("amqp://dev.rabbitmq.com:5672/") do |client|
+  # connection is open and ready to be used
+end
+</code>
+</pre>
+
+As these examples demonstrate, {AMQP.connect} and {AMQP.start} accept either a Hash of connection options or a connection URI string.
+See reference documentation for each method to learn all the options they accept and what the default values are.
+
+
+h3. On Thread#sleep use
+
+When not passing a block to {AMQP.connect}, it is tempting to "give connection some time to get through" by using Thread#sleep. Unless you are
+running event loop in a separate thread, don't do this. Thread#sleep blocks current thread so if event loop is running the very same current thread,
+blocking it _will also block the event loop_. *When event loop is blocked, no data is sent or received, so connection does not proceed.*
+
+
+h3. Detecting TCP connection failures
+
+When applications connect to the broker, they need to handle connection failures. Networks are not 100% reliable, even with modern system configuration tools
+like Chef or Puppet misconfigurations happen and broker might be down, too. Error detection should happen as early as possible. There are two ways of detecting
+TCP connection failure, the first one is to catch an exception:
+
+<pre>
+<code>
+#!/usr/bin/env ruby
+# encoding: utf-8
+
+require "rubygems"
+require "amqp"
+
+
+puts "=> TCP connection failure handling with a rescue statement"
+puts
+
+connection_settings = {
+  :port     => 9689,
+  :vhost    => "/amq_client_testbed",
+  :user     => "amq_client_gem",
+  :password => "amq_client_gem_password",
+  :timeout        => 0.3
+}
+
+begin
+  AMQP.start(connection_settings) do |connection, open_ok|
+    raise "This should not be reachable"
+  end
+rescue AMQP::TCPConnectionFailed => e
+  puts "Caught AMQP::TCPConnectionFailed => TCP connection failed, as expected."
+end
+</code>
+</pre>
+
+{AMQP.connect} (and, subsequentily, {AMQP.start}) will raise {AMQP::TCPConnectionFailed} if connection fails. Code that catches it can write to log
+about the issue or use retry to execute begin block one more time. Because initial connection failures are due to misconfiguration or network outage, reconnection
+to the same endpoint (hostname, port, vhost combination) will result in the same issue over and over. TBD: failover, connection to the cluster.
+
+Alternative way of handling connection failure is with an errback (a callback for specific kind of error):
+
+<pre>
+<code>
+#!/usr/bin/env ruby
+# encoding: utf-8
+
+require "rubygems"
+require "amqp"
+
+puts "=> TCP connection failure handling with a callback"
+puts
+
+handler             = Proc.new { |settings| puts "Failed to connect, as expected"; EM.stop }
+connection_settings = {
+  :port     => 9689,
+  :vhost    => "/amq_client_testbed",
+  :user     => "amq_client_gem",
+  :password => "amq_client_gem_password",
+  :timeout        => 0.3,
+  :on_tcp_connection_failure => handler
+}
+
+
+AMQP.start(connection_settings) do |connection, open_ok|
+  raise "This should not be reachable"
+end
+</code>
+</pre>
+
+:on_tcp_connection_failure option accepts any object that responds to #call.
+
+If you connect to the broker from a code in a class (as opposed to top-level scope in a script), Object#method can be used to pass object method as a handler
+instead of a Proc.
+
+TBD: provide an example
+
+
+h3. Detecting authentication failures
+
+Another reason why connection may fail is authentication failure. Handling authentication failure is very similar to handling initial TCP
+connection failure:
+
+<pre>
+<code>
+#!/usr/bin/env ruby
+# encoding: utf-8
+
+require "rubygems"
+require "amqp"
+
+puts "=> TCP connection failure handling with a callback"
+puts
+
+handler             = Proc.new { |settings| puts "Failed to connect, as expected"; EM.stop }
+connection_settings = {
+  :port     => 5672,
+  :vhost    => "/amq_client_testbed",
+  :user     => "amq_client_gem",
+  :password => "amq_client_gem_password_that_is_incorrect #{Time.now.to_i}",
+  :timeout        => 0.3,
+  :on_tcp_connection_failure => handler,
+  :on_possible_authentication_failure => Proc.new { |settings|
+                                            puts "Authentication failed, as expected, settings are: #{settings.inspect}"
+
+                                            EM.stop
+                                          }
+}
+
+AMQP.start(connection_settings) do |connection, open_ok|
+  raise "This should not be reachable"
+end
+</code>
+</pre>
+
+In case you wonder why callback name has "possible" in it: {http://bit.ly/mTr1YN AMQP 0.9.1 spec} requires broker implementations to
+simply close TCP connection without sending any more data when an exception (such as authentication failure) occurs before AMQP connection
+is open. In practice, however, when broker closes TCP connection between successful TCP connection and before AMQP connection is open,
+it means that authentication has failed.
+
+
+
+h2. In Web applications (Ruby on Rails, Sinatra, Merb, Rack)
+
+h3. With Unicorn
+
+TBD
+
+
+h3. With Thin
+
+TBD
+
+
+h3. With Goliath
+
+TBD
+
+
+h3. With Passenger
+
+TBD
+
+
+
+h2. What to read next
+
+TBD
+
+
+h2. Tell us what you think!
+
+Please take a moment and tell us what you think about this guide on "Ruby AMQP mailing list":http://groups.google.com/group/ruby-amqp:
+what was unclear? what wasn't covered? maybe you don't like guide style or grammar and spelling are incorrect? Readers feedback is
+key to making documentation better.
+
+If mailing list communication is not an option for you for some reason, you can "contact guides author directly":mailto:michael@novemberain.com?subject=amqp%20gem%20documentation