[ 
https://issues.apache.org/jira/browse/QPID-2363?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12805478#action_12805478
 ] 

Rob Godfrey commented on QPID-2363:
-----------------------------------

I think its sort of strange to deliberately stop 0-8 from understanding it...

You don't need to understand all of 0-10 to decode the map message - you just 
need to understand the encoding used (which happens to be the 0-10 encoding of 
maps in this case)

I would much rather not have the 0-8 client fall over if it receives such a 
message, and instead just have it decode it.

On a separate point... are we locked into using "amqp/map" as the MIME type 
(i.e. is that what other clients are already using).  It would make more sense 
to call it "amqp-0-10/map" as AMQP 1-0 will no doubt have a different map 
encoding... 

> JMS Map Message Should Support AMQP 0-10 Encoded Map As Message Body
> --------------------------------------------------------------------
>
>                 Key: QPID-2363
>                 URL: https://issues.apache.org/jira/browse/QPID-2363
>             Project: Qpid
>          Issue Type: New Feature
>          Components: Interop Testing, Java Client
>            Reporter: Rajith Attapattu
>            Assignee: Rajith Attapattu
>             Fix For: 0.7
>
>         Attachments: QPID-2363.patch
>
>
> As part of the new API initiative in Qpid, the C++ client and python client 
> have added support for a map message, where the content is a map of key,value 
> pairs encoded using the AMQP 0-10 encoding for Maps.
> Currently the JMS Map message body is encoded as an opaque binary blob. 
> We need to add support for the JMS Map message implementation to set an AMQP 
> 0-10 encoded Map for the message body. 
> This allows inteoperability btw JMS Map messages and c++, python map messages.
> The content-type for the proposed map message is "amqp/map".
> This feature is only added to the 0-10 code path as the versions below AMQP 
> 0-10 does not have any native support for encoding maps.
> The new map message format will be the default for any map message created by 
> a 0-10 Session.
> If it needs to send any messages using the old map message format it will 
> need to use the following jvm arg "-Dqpid.use_legacy_map_message=true"
> Once the addressing support is finalized we could also add a per destination 
> flag to indicate if legacy messages needs to be used or not.

-- 
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:[email protected]

Reply via email to