[ 
https://issues.apache.org/jira/browse/PROTON-711?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14266464#comment-14266464
 ] 

Robbie Gemmell commented on PROTON-711:
---------------------------------------

Per the above, the bulk of the changes here have been reverted via PROTON-792. 
The test code added in the 1st and 4th commit here for the existing/remaining 
functionality have been left in place.

> [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)

Reply via email to