On 06/16/2015 05:12 PM, Gordon Sim wrote:
I'd like to get a fix in for
https://issues.apache.org/jira/browse/QPID-6256. It improves the sense
of interoperability as you don't need explicit options to get
qpid::messaging to communicate to a 1.0 broker/intermediary.
I have a patch for that I just need to retest and get committed. Ideally
I'd like to add some option to also allow the client to be configured to
try the protocols in the other order.
This should not take more than a few days, so I'll aim to have it on
trunk by the end of the week unless there are objections.
I have committed a change that improves the control users have over
protocol version used (i.e. AMQP 0-10 v AMQP 1.0).
Specifically:
* the 'protocol' connection option now supports specifying multiple
protocols to try in order (as a coma separated list)
* the protocol defaults, i.e. the value assumed if the 'protocol'
connection option is not specified, can now be set via the client
config file (e.g. protocol-defaults=amqp1.0,amqp0-10) or an
environment variable (e.g QPID_PROTOCOL_DEFAULTS=amqp1.0,amqp0-10)
* if neither the connection option nor the defaults are specified
all valid versions will be tried
By default, with no connection options needed, the qpid::messaging
client can now connect to any compliant 1.0 broker. Even though 0-10 is
still the default, if the broker responds correctly[1], the client will
try 1.0 and continue with that if accepted.
The order in which these are tried can be reversed to prefer 1.0, by
editing the client conf file or specifying the environment variable.
[1] At present this excludes qpid-dispatch unfortunately, due to
https://issues.apache.org/jira/browse/PROTON-915
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
