qpid-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rajith Attapattu (JIRA)" <qpid-...@incubator.apache.org>
Subject [jira] Created: (QPID-2226) content types should be handled consistently across all clients
Date Wed, 02 Dec 2009 21:26:20 GMT
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
          Components: Interop Testing
            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 is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project:      http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org


Mime
View raw message