[
https://issues.apache.org/jira/browse/PROTON-711?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14266458#comment-14266458
]
ASF subversion and git services commented on PROTON-711:
--------------------------------------------------------
Commit 4191590ec121027b0590242a42bdae2032b3126d in qpid-proton's branch
refs/heads/master from Robert Gemmell
[ https://git-wip-us.apache.org/repos/asf?p=qpid-proton.git;h=4191590 ]
PROTON-792: Revert "PROTON-711: add support (disabled by default) for using a
byte value for destination type annotations during inbound transformation"
This reverts commit 960eeff9eefa5b8dc52de356d1118ae0b017a319.
> [contrib/proton-jms] add support to message transformers for more efficient
> destination type annotation value
> -------------------------------------------------------------------------------------------------------------
>
> Key: PROTON-711
> URL: https://issues.apache.org/jira/browse/PROTON-711
> Project: Qpid Proton
> Issue Type: Improvement
> Reporter: Robbie Gemmell
> Assignee: Robbie Gemmell
> Fix For: 0.8
>
>
> [contrib/proton-jms] add support to transformers for more efficient
> destination type annotation values
> Historically the JMSDestination and JMSReplyTo values have had their
> Destination type information conveyed as strings that contain a comma
> seperated set of attributes from "queue", "topic", and "temporary". This isnt
> particularly efficient, either on the wire or when determining the value
> during inbound or outbound transformation on clients/brokers.
> The OASIS JMS Mapping for AMQP is likely to use a byte to encode this
> information more efficiently. This change will add initial support (disabled
> by default to retain existing behaviour, brokers can enable it as and when
> they determine it appropriate) for using such a byte encoding within the
> proton-jms transformer code.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
