[rabbitmq-discuss] Erlang client: unregistering confirm/return/flow handler

• Previous message: [rabbitmq-discuss] Erlang client: unregistering confirm/return/flow handler
• Next message: [rabbitmq-discuss] return callback works only once
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Hi Ivan,
At Mon, 16 Jul 2012 13:28:51 +0200,
Ivan Dyachkoff wrote:
> Currently the only way to unregister any type of handler mentioned in subject
> is to kill pid that was registered as handler. That gives us error message in
> log "Channel (<...>): Unregistering confirm handler <...> because it died."
> which is not actually an error.
> Would be nice to have methods in amqp_channel module to unregister 3 types of
> handlers, so in 'terminate' we can call say "unregister_confirm_handler" and
> terminate gracefully.
> What do you think?

That sounds reasonable, I'll file a bug.

--
Francesco * Often in error, never in doubt

• Previous message: [rabbitmq-discuss] Erlang client: unregistering confirm/return/flow handler
• Next message: [rabbitmq-discuss] return callback works only once
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]