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

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

Commit 6255d0b4698472d45a15550a217be0aa07277db2 in qpid-proton's branch 
refs/heads/main from Clifford Jansen
[ https://gitbox.apache.org/repos/asf?p=qpid-proton.git;h=6255d0b46 ]

PROTON-2647: make send-abort example handle variations in number of FLOW events


> Fix FLOW event processing in send-abort example.
> ------------------------------------------------
>
>                 Key: PROTON-2647
>                 URL: https://issues.apache.org/jira/browse/PROTON-2647
>             Project: Qpid Proton
>          Issue Type: Bug
>          Components: proton-c
>    Affects Versions: proton-c-0.37.0
>            Reporter: Clifford Jansen
>            Assignee: Clifford Jansen
>            Priority: Major
>             Fix For: proton-c-0.38.0
>
>
> The current send-abort example program relies on a cadence of FLOW events, 
> some self generated and some originating from the peer.  This cadence can be 
> disrupted by the timing of frames at each peer.  They can also be disrupted 
> by additional self generated FLOW frames in the case of smaller 
> max-frame-size configurations which may be chunked between event batches.
> The program can be made deterministic by not counting FLOW events but by 
> checking the actual state change that may be expected with a FLOW event.
>  



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to