You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Rajith Attapattu (JIRA)" <qp...@incubator.apache.org> on 2009/12/02 22:26:20 UTC
[jira] Created: (QPID-2226) content types should be handled
consistently across all clients
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
[jira] Commented: (QPID-2226) content types should be handled
consistently across all clients
Posted by "Rajith Attapattu (JIRA)" <qp...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/QPID-2226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12805584#action_12805584 ]
Rajith Attapattu commented on QPID-2226:
----------------------------------------
qpid/map; encoding=amqp-0-10 is what you are envisioning?
I am not very familiar with mime type formats - but from what I've seen it looks correct. However I stand to be corrected
> 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
[jira] Commented: (QPID-2226) content types should be handled
consistently across all clients
Posted by "Rafael H. Schloming (JIRA)" <qp...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/QPID-2226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12805579#action_12805579 ]
Rafael H. Schloming commented on QPID-2226:
-------------------------------------------
What we're using for map messages in the API is right now just an 0-10 map, however semantically I think of it as a qpid map message that happens to incidentally use an 0-10 map encoding, however we may change the encoding in the future. So I think the mime type should primarily indicate that it is a qpid map message, but somehow also indicate the specific encoding. I'm not a mime type expert, so I'm not sure of the correct way to do this. I know some mime types have parameters that indicate encoding, e.g.:
text/plain; charset=utf8
So that might suggest something like:
qpid/map; encoding=blah
> 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