Robbie Gemmell commented on PROTON-961:

I don't think there would be a need for that in hindsight. I overlooked that 
this should only have an effect if the Messenger has set a *local* 
maxFrameSize, which is what I think you changed it to do (with this also 
influencing the remote max frame size as seen by the other messenger instance). 
If it doesnt do that (as I don't think it does currently?) then I dont think it 
should have a problem (unless 2^31-1 transfer frames are recieved without a 
flow going in the opposite direction on the session), because the advertised 
incoming window will always be set to 2^31-1 independent of the frame size or 
number of transfer frames received.

> messenger doesn't handle multi-frame transfers
> ----------------------------------------------
>                 Key: PROTON-961
>                 URL: https://issues.apache.org/jira/browse/PROTON-961
>             Project: Qpid Proton
>          Issue Type: Bug
>          Components: proton-c
>    Affects Versions: 0.9.1, 0.10, 0.11
>            Reporter: Gordon Sim
> See QPID-6651 for a reproducer.

This message was sent by Atlassian JIRA

Reply via email to