[
https://issues.apache.org/jira/browse/QPID-7683?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15885431#comment-15885431
]
Rob Godfrey commented on QPID-7683:
-----------------------------------
So - my thoughts on this were that we would have some sort of plugin for
mime-types to covert to Objects (and possibly reverse this as well). In future
this could also be potentially used to convert from one mime-type encoding to
another. As is your patch is causing 0-8 and 0-10 to become dependent upon
each other. If we simply used plugins, each protocol plugin could define the
way to interpret/encode the mime-type<->object mappings, and the message
converters would simply need to locate the mime type plugin support.
> Remove knowledge of 0-x encoders from the AMQP 1.0 protocol layers
> ------------------------------------------------------------------
>
> Key: QPID-7683
> URL: https://issues.apache.org/jira/browse/QPID-7683
> Project: Qpid
> Issue Type: Bug
> Components: Java Broker
> Reporter: Keith Wall
> Fix For: qpid-java-7.0
>
> Attachments:
> 0001-QPID-7683-Refactor-AMQP-1.0-module-to-avoid-knowledg.patch
>
>
> Currently the AMQP 1.0 protocol layer makes direct use of BBEncoder (0-10)
> and TypedBytesEncoder (supported by the Qpid Client for the encoding of
> list/map message content for 0-8..0-10). This prevents the 0-x encoders from
> being moved to their respective module.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
