Proton-j: SendLink flow control
Hello All! We are using the Proton-J 0.12.0 Amqp library – and built Event Hubs Java Amqp Client on Reactor framework - https://github.com/Azure/azure-event-hubs/tree/master/java. Please validate my assumption w.r.to Sender Flow control: - Current Expectation from Reactor APIs is that – on Sender Link – wait for the onLinkFlow(Event) and rely on “event.getLInk().getRemoteCredit()” to know how many more messages can be Sent on the Link. Proton amqp layer will interpret the FlowFrame and do-the-math of deliveryCounts of Sender and Receiver and the New Credit issued by the Sender. - This API Contract essentially means that, Frameworks building atop Reactor API – will need to implement FlowControl (will queue-up all the Messages until it receives the FlowFrame). Do you folks have plans to move this functionality of flow control into the Proton-API offering – as every implementation will need it. Thanks! Sree
Re: Qpid Proton set session id
Connecting with a different python library, I get a sessionId of -1. When I connect with the qpid-proton library, I get a sessionId of 0. For both of these, no matter how many connections I make, I get the same sessionId. So it appears this is getting set somewhere, but I can't seem to find it anywhere. -- View this message in context: http://qpid.2158936.n2.nabble.com/Qpid-Proton-set-session-id-tp7640698p7640711.html Sent from the Apache Qpid Proton mailing list archive at Nabble.com.
Re: Does anyone read this list?
+1 on Alan's comments Qpid has lots of components and a single cohesive user list as the "entry point" is the best way to foster community IMHO. F. On 24/03/16 21:29, Alan Conway wrote: On Thu, 2016-03-24 at 18:23 +, Troy Daniels wrote: This was also the only mailing list that I found a reference to when I was looking at the proton site. Which makes me agree that you (or at least the documentation) are trying to recruit developers rather than users. :-) It is a historical accident I think. The Qpid project has a lot of interesting and inter-related things going on around AMQP. Proton is an important sub-project but not the only one. In the early days it was felt by some that proton really needed its own list, but I think in practice that has turned out to be a bad idea that just isolates and breaks up discussions. The user list is not so heavily trafficked and most interesting discussions that touch on proton also touch on other Qpid projects. So I generally post to the user list but I keep an eye on this one. I'd change the reference on the site if I wasn't afeared of a firestorm. Anyone who objects please complain on the proton list only ;)
