Message always publish to localhost. Reuse base 'channel' method to publ...

[pavel-drobushevich]

...ish and subscribe on one instance (via change connection host to not localhost).

[majek]

I'm not a ruby person. What's the difference?

[majek]

I'm not a ruby person. What's the difference?

[pavel-drobushevich]

Old code call following method:
AMQP::Exchange.default
Source code for this method:
https://github.com/ruby-amqp/amqp/blob/master/lib/amqp/exchange.rb (line 149 and below)
This method has one argument - channel to connect, If this argument is not provided exchange creates default channel which connects to localhost. It is not expected, because FibonacciRpcClient has own channel and in my case it was configured to remote RabbitMQ installation, but as result message try to send to default localhost channel (I don't have local instance).
There are two possible:

1. Use exist channel to create exchange
   self.channel.default_exchange
2. Send exist channel to this method
   AMQP::Exchange.default(self.channel)

[pavel-drobushevich]

Old code call following method:
AMQP::Exchange.default
Source code for this method:
https://github.com/ruby-amqp/amqp/blob/master/lib/amqp/exchange.rb (line 149 and below)
This method has one argument - channel to connect, If this argument is not provided exchange creates default channel which connects to localhost. It is not expected, because FibonacciRpcClient has own channel and in my case it was configured to remote RabbitMQ installation, but as result message try to send to default localhost channel (I don't have local instance).
There are two possible:

1. Use exist channel to create exchange
   self.channel.default_exchange
2. Send exist channel to this method
   AMQP::Exchange.default(self.channel)

[michaelklishin]

The idea is to not allocate a new channel implicitly. In practical terms, it makes no difference for tutorials but may lead to people doing this unknowingly in real world code, over and over.

[michaelklishin]

The idea is to not allocate a new channel implicitly. In practical terms, it makes no difference for tutorials but may lead to people doing this unknowingly in real world code, over and over.