[PROTON-636] remove confusing default for session capacity and allow disabling it

• Type: Improvement
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Fix Version/s: proton-c-0.23.0
• Component/s: proton-c
• Labels: framing
• Assignee: Alan Conway
• Reporter: Rafael H. Schloming
• Created: 28/Jul/14 12:15
• Updated: 26/May/18 19:36
• Resolved: 11/Apr/18 10:04

Description

Original title: setting a 1MB frame size results in an undesirably small session window)

Description, from PROTON-1739:

The session has a default 'incoming capacity' of 1MB, which actually has no effect by default and leads to unexpected behaviour while changing other configuration. It should be removed.

The value is used when the engine decides what incoming session window to set on Flow frames, but only if a specific frame size is configured for the transport, which it isn't by default. If a specific frame size is set, then any session capacity really needs to be set based on it in order to be appropriate, the default being fixed as it is leads to unexpectedly low window sizes in many cases which will impact performance in unexpected ways. Its confusing that setting frame size results in completely different behaviour than before for another thing (window size) which perhaps hasn't been configured at all, and the existing behaviour is also such that you cant turn it off.

Issue Links

• incorporates: PROTON-1523 [proton c] API unclear how incoming_capacity and max_frame work
• is related to: PROTON-1809 [python, ruby] Unable to receive messages when max-frame-size is set to more than 2^20
• is related to: PROTON-1739 remove confusing default for session capacity and allow disabling it