[
https://issues.apache.org/jira/browse/QPID-8026?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16245584#comment-16245584
]
Keith Wall commented on QPID-8026:
----------------------------------
The filter would need to know the message's encoded size (in AMQP 1.0). This
is known for AMQP 1.0, but won't be known converted messages. The Broker
probably ought to avoid re-calculating converted messages size (only to find a
link can't take it), so it may want to cache it. Separately, there is an
interesting decision to be made about how the feature interacts with message
grouping.
> [Java Broker] [AMQP 1.0] Add support for max-message-size on consumer attach
> ----------------------------------------------------------------------------
>
> Key: QPID-8026
> URL: https://issues.apache.org/jira/browse/QPID-8026
> Project: Qpid
> Issue Type: Improvement
> Components: Java Broker
> Affects Versions: qpid-java-broker-7.0.0
> Reporter: Rob Godfrey
>
> QPID-7957 added support for sending the max-message-size on producer attaches
> *sent* to the broker, but there is currently no support in the broker for the
> case where a consumer attaches a link which asserts that the consumer is
> unable to receive messages above a certain size on that link.
> In this case the consumer should, I think, behave as if a filter had been
> applied which simply excludes from the possibility of delivery any message
> which (when converted into an AMQP 1.0 payload) would be above the given size.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
