Hi, As we are doing a bit a re-factoring for the new 0.10 client I would suggest that we re-evaluate our JMS URL convention. I would like to simplify the current one and use the following protocols: - amqp://host:port/virtual_host - loopback://virtual_host In addition to that we would use the following properties: - amqp.transportType with default value "tcp" (at the minute we are only supporting this type) - amqp.encryption with currently supported values "plain", "ssl"; default = plain
Regarding clustering I would suggest that we use the properties: amqp.brokerURL.1; amqp.brokerURL.2; ... ; amqp.brokerURL.n When specific transport type or/and encryption must be used we would also add the corresponding indexed properties i.e. amqp.encryption.2=ssl For security we would also use properties: amqp.username; amqp.password; amqp.keystore etc. Regarding destinations, I would suggest that we provide a simple admin class that let create/delete queues and topics. I would not provide support for declaring destination as JNDI properties. When a destination is looked up I would check with the broker that this destination exists. Arnaud
