[
https://issues.apache.org/jira/browse/QPID-6256?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14590108#comment-14590108
]
ASF subversion and git services commented on QPID-6256:
-------------------------------------------------------
Commit 1686078 from [~gsim] in branch 'qpid/trunk'
[ https://svn.apache.org/r1686078 ]
QPID-6256: Improved handling of protocol version incompatibilities
* 0-10 path no longer hans on open when connecting to a broker not
supporting that version
* 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 (currently amqp0-10, then amqp1.0
but this may change in a future version)
> try AMQP 1.0 if 0-10 not supported
> ----------------------------------
>
> Key: QPID-6256
> URL: https://issues.apache.org/jira/browse/QPID-6256
> Project: Qpid
> Issue Type: Bug
> Components: C++ Client
> Affects Versions: 0.30
> Reporter: Gordon Sim
> Assignee: Gordon Sim
>
> The qpid::messaging client defaults to 0-10, though the version can be
> explicitly specified also. If the broker doesn't support 0-10, but does
> support 1.0 and assuming that 1.0 support in the client is enabled and the
> application didn't explicitly request 0-10, the client should try 1.0.
> This would make interoperability easier as it wouldn't require specific
> connection options to choose 1.0.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
