This is curious, because Subscribe(Type, string) and Unsubscribe(Type, string), both receive an string with the InputQueue's address. However neither my current code, nor previous one, used this parameter to declare actual bindings/routes to setup so subscripted messages end up reaching the desired queue.. And instead they use RabbitMqMessageQueue's InputQueue/InputQueueAddress as target of subscription.

This is not a problem here, but I guess if this 'inputQueueAddress' parameter which gets passed to Subscribe/Unsubscribe is a requirement for other queue implementation and this is how it ended up here. Also, I dont know which exact implication would have relaying on 'inputQueueAddress' parameter instead of using the class' internal properties being used actually.