John O'Hara wrote:
Very well considered, and highly flexible.Compatible with where AMQP1.0 is
heading (wrt TLS handling -- balance of opinion is that TLS will be on the
same port, as it would be for Kerberos based encryption).
Missed out a TLS example:
amqp+tls://foo:b...@tcp:host1:1234/vhost?clientid=baz
I think it's cleaner to put modifiers like TLS into the protocol identifier
rather than the URL scheme:
amqp://foo:b...@tcp+tls: host:...
That gives greater flexibility over protocols used in the host list and avoids
the problem of mis-matching modifiers and protocols, e.g. if we have an
infiniband protocol then what would amqp+tls://ib:inifinibandstuff/... mean?
What do you think?
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscr...@qpid.apache.org
