[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] (MQTT-251) Return server assigned client id to client
[ https://issues.oasis-open.org/browse/MQTT-251?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=59324#comment-59324 ] Andrew Schofield commented on MQTT-251: --------------------------------------- It's true that the biggest use will be the first connect for a clean session false client. The client doesn't want to make up a client id because it can't guarantee uniqueness, but it does want to reconnect with the same client id so it can maintain session state on the server. > Return server assigned client id to client > ------------------------------------------ > > Key: MQTT-251 > URL: https://issues.oasis-open.org/browse/MQTT-251 > Project: OASIS Message Queuing Telemetry Transport (MQTT) TC > Issue Type: Improvement > Components: futures > Reporter: Allan Stockdill-Mander > > In the 3.1.1 specification section 3.1.3.1 http://docs.oasis-open.org/mqtt/mqtt/v3.1.1/os/mqtt-v3.1.1-os.html#_Toc398718031 it is permitted for a client to connect with a zero length client id, the server internally uses a unique identifier for that client but the client does not know the idenfitier and is required to connect with clean session true. -- This message was sent by Atlassian JIRA (v6.2.2#6258)
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]