[
https://issues.apache.org/jira/browse/QPID-2226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justin Ross updated QPID-2226:
------------------------------
Component/s: (was: Interop Testing)
> content types should be handled consistently across all clients
> ---------------------------------------------------------------
>
> Key: QPID-2226
> URL: https://issues.apache.org/jira/browse/QPID-2226
> Project: Qpid
> Issue Type: Improvement
> Reporter: Rajith Attapattu
>
> Content types specified in messages should be handled in a consistent way
> across all clients.
> At the minimum I believe all Qpid clients should support
> 1. text/plain , text/xml (how is encoding handled? )
> 2. application/octet-stream
> 3. Map messages. Currently JMS specifies it as jms/map-message.
> Maybe we could name it as "qpid/map-message"
> Obviously item 3 will be Qpid specific.
> Python and C++ already have work in progress to support Map messages and
> eventually Ruby.
> However what is important is that all clients in Qpid handled these content
> types in a consistent manner.
> This will ensure we interoperate well between different language clients.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
