|
Mark, Dominik,
I don't want to break existing applications (at least for 6 to 12
months :-) . This means that 3.1 must be the default for now if
we don't automatically fall back. And yes, having a new major
version of the clients could enable us to switch the default.
If we do automatically fall back, then having 3.1.1 as the default
is the obvious choice, as most, if not all servers will support
3.1 as well as 3.1.1. If you try 3.1 first you will be stuck with
that. The downside is an extra connect cycle.
I prefer the option "try 3.1.1 first and automatically try 3.1
under the covers if that fails". Then applications don't have to
change, and they can connect easily to either 3.1 or 3.1.1 servers
(assuming other differences in the protocol versions are
minimal). And as I said we can have a connect option to turn off
automatic fall back if you don't want it.
Ian
On 28/01/14 14:42, Marc L Cohen wrote:
Been worrying about what
direction this would take for a while. As long as there is a
way to specify the non-default, I'm okay with it, as we need
to be able to test our servers for both. And I would hate to
see a path taken that would break existing clients on 3.1
existing servers, so if we go for 3.1.1 try first, I would
definitely like to see it fall back and retry 3.1 on failure
to connect.
Marc L. Cohen
MessageSight Test/Development
Internet:mlcohen@xxxxxxxxxx
also at:teddybbear@xxxxxxx
(512) 286-5744 (T/L 363-5744)
FAX (512) 973-4293
 Ian Craggs
---01/28/2014 08:22:28 AM---Hi All, I have been thinking about
the how the Paho clients would support MQTT
From: Ian Craggs
<icraggs@xxxxxxxxxxxxxxxxxxxxxxx>
To: General development discussions for
paho project <paho-dev@xxxxxxxxxxx>,
Date: 01/28/2014 08:22 AM
Subject: [paho-dev] MQTT 3.1.1 support for
Paho clients
Sent by: paho-dev-bounces@xxxxxxxxxxx
Hi All,
I have been thinking about the how the Paho clients would
support MQTT
3.1.1 in their interfaces.
1) My first thought was to add a connect option to select a
3.1.1
connection, with a 3.1 connection being the default for the
time being.
2) I've just thought that by default we could attempt a 3.1.1
connection, and then attempt a 3.1 connection automatically if
the first
failed. Then application programs would not have to change.
There could
be a connect option to say not to do this if you really didn't
want it to.
Which would prefer? Any other options?
Ian
_______________________________________________
paho-dev mailing list
paho-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/paho-dev
_______________________________________________
paho-dev mailing list
paho-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/paho-dev
|
