[
https://issues.apache.org/jira/browse/QPID-7171?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gordon Sim updated QPID-7171:
-----------------------------
Description:
The 0-10 path in qpid::messaging now automatically decodes AMQP 0-10 maps and
lists (identified by their content type) in order to populate the
content-object of the message and give similar behaviour to the 1.0 path.
This is however a change in behaviour and may not be desired by all legacy
users. There is a connection level option to disable this feature. However
requiring every connection to be explicitly configured is not always desirable
either. It would be preferable to allow the behaviour to be controlled as a
client option, via environment variables or through the client config file.
was:
The 0-10 path in qpid::messaging now automatically decodes AQMP 0-10 maps and
lists (identified by their content type) in order to populate the
content-object of the message and give similar behaviour to the 1.0 path.
This is however a change in behaviour and may not be desired by all legacy
users. There is a connection level option to disable this feature. However
requiring every connection to be explicitly configured is not always desirable
either. It would be preferable to allow the behaviour to be controlled as a
client option, via environment variables or through the client config file.
> Allow disable-auto-decode to be set via env var or conf file
> ------------------------------------------------------------
>
> Key: QPID-7171
> URL: https://issues.apache.org/jira/browse/QPID-7171
> Project: Qpid
> Issue Type: Improvement
> Components: C++ Client
> Affects Versions: qpid-cpp-0.34
> Reporter: Gordon Sim
> Assignee: Gordon Sim
>
> The 0-10 path in qpid::messaging now automatically decodes AMQP 0-10 maps and
> lists (identified by their content type) in order to populate the
> content-object of the message and give similar behaviour to the 1.0 path.
> This is however a change in behaviour and may not be desired by all legacy
> users. There is a connection level option to disable this feature. However
> requiring every connection to be explicitly configured is not always
> desirable either. It would be preferable to allow the behaviour to be
> controlled as a client option, via environment variables or through the
> client config file.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
