Details
-
Improvement
-
Status: Closed
-
Major
-
Resolution: Done
-
None
-
None
-
None
-
None
Description
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.