[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=34666#action_34666 ] Richard Coppen commented on MQTT-55: ------------------------------------ Currently this is no covered at all in the spec. Nothing prevents two connects being flowed. We should do something to clarify, narrowed down to three options below: 1. forbid second connect on same TCP Connection in all five cases 2. allow it only in the case where the client ID is the same (2 - 5). would have to specify what should happen if second connect were to fail 3. allow it in all five cases > 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]