[OASIS Issue Tracker] (MQTT-251) Return server assigned client id to client

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

    [ https://issues.oasis-open.org/browse/MQTT-251?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=59041#comment-59041 ] 

Nick O'Leary commented on MQTT-251:
-----------------------------------

If the client wants the server to generate the ID in order to minimise bytes on the wire, if the server then sends the ID back to the client, no saving has been made.

The client should be able to indicate in the connect packet whether it wants the server to send the ID back (presumably in the CONNACK).

> 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)