docs/ConnectingToTheBroker.textile in amqp-0.9.10 vs docs/ConnectingToTheBroker.textile in amqp-1.0.0.pre1
- old
+ new
@@ -1,14 +1,10 @@
# @title Ruby amqp gem: Connecting to the broker, integrating with Ruby on Rails, Merb and Sinatra
h1. Connecting to the broker, integrating with Ruby on Rails, Merb and Sinatra
-h2. This Documentation Has Moved to rubyamqp.info
-amqp gem documentation guides are now hosted on "rubyamqp.info":http://rubyamqp.info.
-
-
h2. About this guide
This guide covers connection to an AMQP broker from standalone and Web applications,
connection error handling, authentication failure handling and related issues.
@@ -358,10 +354,10 @@
EventMachine.stop if EventMachine.reactor_running?
end
</code>
</pre>
-In case you are wondering why the callback name has "possible" in it, {http://bit.ly/mTr1YN AMQP 0.9.1 spec} requires broker implementations to
+In case you are wondering why the callback name has "possible" in it, {http://bit.ly/amqp091spec AMQP 0.9.1 spec} requires broker implementations to
simply close the TCP connection without sending any more data when an exception, such as authentication failure, occurs before the AMQP connection
is open. In practice, however, when a broker closes a TCP connection after a successful TCP connection has been established but before an AMQP connection is open,
it means that authentication has failed.