Great article and module! A few questions…

1. Does this support persistent/durable queues for subscriptions, such that if a receiving/subscribing client goes down, it will not lose messages and pick up from where it left off once it comes back on line?
2. Does this support multiple clients being subscribed to the same queue, in the case that you want to increase message throughput? How would you configure/code that with BunnyBus?
3. As for queue names, do they need to be unique, or is there some kind of automatic namespacing automatically provided under the covers? If unique naming is required, to what scope (universally, within each app/client, within each node/host, etc.)?