Hello Mike,
Thank you and I do understand the limitation.
The question is why such a restriction ?
Isn't clientId sufficient ? why hard bind mqtt connect message to transport TCP specific connect ?
Client health alive or not can be achieved by ping message.
On Thursday, September 22, 2016 12:25 PM, Mike Tran <miketran@xxxxxxxxxx> wrote:
Based on the content of the link you mentioned https://issues.oasis-open.org/browse/MQTT-55: `The Connect Packet MUST be the first packet sent
from a client to the server. A client can only flow the Connect Packet
once per TCP Session. The Server MUST process a second Connect Packet sent
from a client as a protocol violation and disconnect the client. `It is very clear to me that subsequence Connect packets
on the same network connection will be considered as a protocol violation,
so the server must close the network connection regardless of the client
ID. Most MQTT clients do not allow you to send connect packet if the client
is currently connected. --Regards,
Mike Tran
From:
foomail123 <foomail123@xxxxxxxxx>To:
"mosquitto-dev@xxxxxxxxxxx"
<mosquitto-dev@xxxxxxxxxxx>Date:
09/21/2016 11:52 AMSubject:
[mosquitto-dev]
Multiple MQTT Connect messages over same TCP/IP transport connectionSent by:
mosquitto-dev-bounces@xxxxxxxxxxx
Hello,I have a question regarding multiple
MQTT Connect messages over same TCP/IP transport connection.Per my understanding, and belowPer: https://issues.oasis-open.org/browse/MQTT-55The subsequent connections are to
be handled by broker as long at clientId is same, is this right ?When broker receives subsequent MQTT
Connect with different clientId, is the MQTT Connect packet dropped ? Is
the underlying TCP/IP connection from that client also dropped ?Any pointers/references is appreciated.Thank you. _______________________________________________
mosquitto-dev mailing list
mosquitto-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe
from this list, visit
https://dev.eclipse.org/mailman/listinfo/mosquitto-dev
