[ 
https://issues.apache.org/jira/browse/PROTON-636?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16433707#comment-16433707
 ] 

ASF subversion and git services commented on PROTON-636:
--------------------------------------------------------

Commit d58bd7154558a3be3a68dfee71f08c7d76bad958 in qpid-proton's branch 
refs/heads/master from [~gemmellr]
[ https://git-wip-us.apache.org/repos/asf?p=qpid-proton.git;h=d58bd71 ]

PROTON-636, PROTON-1809, PROTON-1523: update session capacity api doc to 
clarify its behaviour


> remove confusing default for session capacity and allow disabling it
> --------------------------------------------------------------------
>
>                 Key: PROTON-636
>                 URL: https://issues.apache.org/jira/browse/PROTON-636
>             Project: Qpid Proton
>          Issue Type: Improvement
>          Components: proton-c
>            Reporter: Rafael H. Schloming
>            Assignee: Alan Conway
>            Priority: Minor
>              Labels: framing
>             Fix For: proton-c-0.23.0
>
>
> 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.



--
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

Reply via email to