[
https://issues.apache.org/jira/browse/PROTON-1828?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robbie Gemmell updated PROTON-1828:
-----------------------------------
Issue Type: New Feature (was: Bug)
> add ability to limit outgoing frame sizes
> -----------------------------------------
>
> Key: PROTON-1828
> URL: https://issues.apache.org/jira/browse/PROTON-1828
> Project: Qpid Proton
> Issue Type: New Feature
> Components: proton-j
> Affects Versions: proton-j-0.26.0
> Reporter: Robbie Gemmell
> Assignee: Robbie Gemmell
> Priority: Major
> Fix For: proton-j-0.27.0
>
>
> Current, proton-j (and c) will send the largest frames it can as permitted by
> a peers max-frame size. Where peers don't set a max frame size, or use a very
> large one, then this typically results in a single outgoing frame being
> emitted, which for large messages can be inefficient and also requires more
> memory than might be desirable. There is no currently way to govern the
> maximum size of the outgoing frames (besides the peers advertised max frame
> size), such a mechanism should be added.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
