[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] Commented: (MQTT-55) What should happen if a client issues multiple connect calls on the same TCP Connection
[ http://tools.oasis-open.org/issues/browse/MQTT-55?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=34202#action_34202 ]
Nick O'Leary commented on MQTT-55:
----------------------------------
Here is my understanding of the unwritten behaviour:
A CONNECT packet must be the first packet a server receives from a client.
The client MUST not resend a CONNECT at any time.
If a server receives a CONNECT packet from an already connected client, this is a deviation from normal behaviour and the client MUST be disconnected.
> What should happen if a client issues multiple connect calls on the same TCP Connection
> ---------------------------------------------------------------------------------------
>
> Key: MQTT-55
> URL: http://tools.oasis-open.org/issues/browse/MQTT-55
> Project: OASIS Message Queuing Telemetry Transport (MQTT) TC
> Issue Type: Improvement
> Components: core
> Affects Versions: 3.1.1
> Reporter: Richard Coppen
> Fix For: 3.1.1
>
>
> The current specification does not address this situation
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://tools.oasis-open.org/issues/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]