[OASIS Issue Tracker] Commented: (MQTT-55) What should happen if a client issues multiple connect calls on the same TCP Connection

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

    [ http://tools.oasis-open.org/issues/browse/MQTT-55?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=34203#action_34203 ] 

Raphael Cohen commented on MQTT-55:
-----------------------------------

Devil's advocate... Can a client CONNECT, DISCONNECT, CONNECT?

Other protocols (e.g. TLS) do allow this, but I'm not very keen, if at all, to permit this behaviour if it isn't specifically barred. It'd be pretty unusual and the only use case I see is to log in with different credentials without the overhead of re-establishing TCP and may be TLS. Given that any TLS layering has a strong likelihood of also being credential related, this would seem to be somewhat sub-optimal.

> 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