Re: Automated queue creation within a swiftlet

The documentation and API really does not make any of that clear. It's confusing that queueManager.isDefined(queueName) can return true for a regular queue, and you can delete a regular queue when .createQueue is not able to actually create a regular queue. It seems the name is inconsistent and/or misleading?

Since I require persistent queues, I am assuming I need regular queues rather than system queues, but can't actually find documentation of the differences. Is there a functional difference between those queues defined in the config file and those "system" queues that may be created at startup?

i.e is there going to be a functional difference if I switched my extension swiftlet to always "create" all of my necessary queues at startup, vs. having them as regular queues defined in the config file? I am presuming it will affect the ability of those queues to have messages persisted across restarts, but I'm not really sure now.

If the answer is such that I can't have persistent "system" queues managed by my Swiftlet and thus have to use the CLI to manage regular queues, is there then a way I can create a regular one within an extension swiftlet during startup? When i try to do so using the CLI it seems unable to reliably get a CLI connection, usually timing out after 60 seconds. I presume this is somehow related to doing so while the router is still starting up; i.e. the management tree isn't fully enabled?