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

From
OASIS Issues Tracker <>
Date
2013-07-29T19:06:20+00:00
ID
704785665.191375124777810.JavaMail.tomcat@customer-jira
Thread
[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=34204#action_34204 ] 

Nick O'Leary commented on MQTT-55:
----------------------------------

The 3.1 spec says this about DISCONNECT:
 The DISCONNECT message is sent from the client to the server to indicate that it is about to close its TCP/IP connection.

That implies, without spelling it out explicitly, that a TCP connection cannot be reused.


> 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