[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=59310#comment-59310 ] Allan Stockdill-Mander commented on MQTT-251: ---------------------------------------------- In the lifetime of a client the bytes of passing back a client id are likely to be minimal, options are complexity and would this option really be beneficial? If I'm asking the server to assign me a client id and I want to know what that id is presumably it's because I want some state to be stored by the server. Apart from app debugging (which could still use cleansession false) I can't currently think of a good reason to have no session and need your client id (even if it might be nice). In which case we could just formalise it that requesting a server assigned id with cleansession false will result in the id being returned, cleansession true and it will not. > 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]