[
https://issues.apache.org/jira/browse/QPID-4707?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13674604#comment-13674604
]
Andrew Stitcher commented on QPID-4707:
---------------------------------------
Ah, I assumed that qpid::amqp was specific to the new amqp support code.
My mental model was that you had chosen to call the new amqp 1.0 support just
qpid::amqp because it supports the official standardised protocol rather than
the pre-standard 0.10 etc. versions - this makes reasonable sense to me.
But if I look at the code in qpid::amqp much of it is actually 1.0 specific
irrespective of which library it gets built into.
At present the only place in the current tree which isn't protocol specific and
is shared between broker and client is qpid::sys which isn't a good name at all
(and there is indeed stuff in there that isn't actually shared!)
It would definitely be good to have a good set of rules about what goes where
in the tree and then to move everything to suit.
> [AMQP 1.0] provide means of setting more fields in a 1.0 formatted message
> --------------------------------------------------------------------------
>
> Key: QPID-4707
> URL: https://issues.apache.org/jira/browse/QPID-4707
> Project: Qpid
> Issue Type: Bug
> Components: C++ Client
> Affects Versions: 0.22
> Reporter: Gordon Sim
> Assignee: Gordon Sim
> Fix For: 0.23
>
>
> To begin with, the various x-amqp-xxxx properties that are set on receiving a
> message should be recognised when sending a message also.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
