[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=59326#comment-59326 ] Ken Borgendale commented on MQTT-251: ------------------------------------- I very much dislike allowing generated client id with cleansession=0. This just seems like an case of orphaned resources waiting to happen. However, I do not object too much as long as we make it clear that the server is not required to allow cleansession=0 in this case, even if it allows a zero length client id. Returning the generated client id in the CONNACK makes it potentially a 64K long packet which I assume some clients would not like. Of course it is unlikely that any server would construct such a client id, but returning this means that the client knows that the server will not give it a CONNACK which is "too big". > 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]