Mailing-List: contact users-help@qpid.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@qpid.apache.org
Date: Tue, 18 Oct 2016 18:15:18 -0400 (EDT)
From: Chuck Rolke <crolke@redhat.com>
To: users@qpid.apache.org
Message-ID: <901255852.9142683.1476828918269.JavaMail.zimbra@redhat.com>
In-Reply-To: <CANVjZ_RRyTz7qBGmH+P+PX+WEK98+ZfstrMLCzEH8Tr-9-F-8g@mail.gmail.com>
References: <CANVjZ_RRyTz7qBGmH+P+PX+WEK98+ZfstrMLCzEH8Tr-9-F-8g@mail.gmail.com>
Subject: Re: Proton Python on_sendable behavior
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Thread-Topic: Proton Python on_sendable behavior
Thread-Index: zBEJEB1xIX78iihA4c5u88/vbcg1CA==
archived-at: Tue, 18 Oct 2016 22:15:32 -0000


----- Original Message -----
> From: "Justin Ross" <justin.ross@gmail.com>
> To: users@qpid.apache.org
> Sent: Tuesday, October 18, 2016 5:13:27 PM
> Subject: Proton Python on_sendable behavior
> 
> https://gist.github.com/ssorj/1ccf4d1499563722bc419f1e1fac11bf
> 
> In this example, there is still ample credit on the link after the last
> on_sendable() is printed, but on_sendable is never fired again.  Is that
> expected behavior?
> 
> It appears that on_link_flow is only fired when link credit is updated, and
> on_link_flow is the source of all on_sendable events.
> 
> https://github.com/apache/qpid-proton/blob/master/proton-c/bindings/python/proton/handlers.py#L36
> 

When I run this code all messages go to the broker in one frame and the flow and dispositions come back in one frame:

 Frame 46  127.0.0.1:60006  -> 127.0.0.1:5672  ->   transfer [0,0] (0..9)
 Frame 47  127.0.0.1:60006 <-  127.0.0.1:5672 <-    flow [0,0] (10,500), disposition [0] (receiver 0-9) 

You have credit and just got some on_sendable callbacks. What's wrong with what you see?

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
For additional commands, e-mail: users-help@qpid.apache.org