[paho-dev] Maximum messages inflight on Java asynchronous client

[Ian Craggs <icraggs@xxxxxxxxxxxxxxxxxxxxxxx>]

Hello all,

when the Java asynchronous API was written, it used the same maximum 
message inflight limit for QoS 1/2 messages as the synchronous client, 
of 10.

We've had some people report hitting that limit and wanting it to go 
higher.  In the C asynchronous and JavaScript clients, there is no such 
limit, because you can use the callbacks to count how many outstanding 
messages there are, so you can implement any strategy yourself.

We are fixing this under bug 456855: 
https://bugs.eclipse.org/bugs/show_bug.cgi?id=456855.

My first suggestion was to allow the limit to be configurable, which is 
what Bin has implemented, with the default as it was previously, for 
maximum backward compatibility.  However it has been suggested that 
removing the limit altogether would be better (in fact then it would be 
the MQTT message limit, 64k).

Does anyone have any strong feelings either way, or other thoughts or 
suggestions?

Thanks

--
Ian Craggs
icraggs@xxxxxxxxxx                 IBM United Kingdom
Paho Project Lead; Committer on Mosquitto