[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] Updated: (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:all-tabpanel ] Richard Coppen updated MQTT-55: ------------------------------- Proposal: 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. > 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]