Automatically reconnect to hosts if possible.
implement backoff strategies and allow configuring reconnect off
This test case should clean up after itself better, so that running the test suite multiple times need not fail.
1. Automatic reconnection only when connection was not terminated manually.
2. Automatic reconnection should re-subscribe consumers anew exactly once per subscription.
3. On manual reconnection, channels should not be automatically reconnected.
Move heartbeat timing into the driver, check receipt of heartbeats from server side as well.
Added arguments parameter. Will expand with an example later
AMQP connection refused, in case the AMQP server is not installed.
Errors are not always cause to terminate the connection; terminal errors pretty clearly are.
Change default reconnection preference to "false".
Document reconnection strategies.
Remove the "magic" aspect of trying to decide whether the connection was terminated on purpose or by error; it didn't work.  If you want to terminate a connection which has reconnect set to true, first set it to false.
reorganize
serialize
Correct spelling: 'hearbeat' -> 'heartbeat'
Add invocation of connection.heartbeat upon onHeartbeat event
implemented flow control
implemented Queue.purge method
Merge remote-tracking branch 'matt/master' into 0.1.3-reconnect
version up
detect contentType for messages with complex headers
bumped supported node version
Merge pull request #112 from vicapow/master

add support for node 0.8
simplify handling of content_type