[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] Commented: (MQTT-42) Clean session and random client ids
[ http://tools.oasis-open.org/issues/browse/MQTT-42?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=34498#action_34498 ]
Nick O'Leary commented on MQTT-42:
----------------------------------
For MQTT v3.1.1, the following proposal addresses the original concerns raised in this item. This is a non-normative comment at the end of section 3.1.3.1 Client Identifier (wd10).
I have toned down the language from Roger's original "must refuse to do so" as it depends on how such a method is exposed. For example, the Paho Java client provides a static method to generate a valid client id, returned as a String. This can then be passed to an actual client instance for use. The client instance does not know the client id was generated via the convenience method so would have no way to reject it. It would also be valid to generate a 'random' id the first time and the application stores it for future use by the client instance.
--------------------------
Non-normative:
A client implementation may provide a convenience method to randomly generate the Client Identifier. Use of such a method should be actively discouraged when the Clean Session flag is set to 0.
--------------------------
There is then a separate discussion in this thread about possible future enhancements - specifically whether a CleanSession=0 client could be allowed to provide a 0-length Client ID (and the knock-on effects of server generating on etc, reframing ClientID as SessionID). We should not let the future discussion stop us resolving the v3.1.1 part of the discussion.
> Clean session and random client ids
> -----------------------------------
>
> Key: MQTT-42
> URL: http://tools.oasis-open.org/issues/browse/MQTT-42
> Project: OASIS Message Queuing Telemetry Transport (MQTT) TC
> Issue Type: Improvement
> Components: core
> Affects Versions: 3.1.1
> Environment: N/A
> Reporter: Raphael Cohen
> Priority: Minor
> Fix For: 3.1.1
>
>
> Opened on behalf of Roger Light:-
> Hi,
> A lot of MQTT client libraries offer the feature of generating random
> client ids rather than having to supply one. This is good.
> I recently had over 10,000 client connections made to
> test.mosquitto.org using a random client id, but also having set clean
> session to false, which meant that when they disconnected their
> information was stored on the server but there was basically no chance
> they could reconnect.
> It would be nice to have a comment in the spec suggesting that
> implementations may offer to generate random client ids but that they
> must refuse to do so if clean session is set to false.
> Cheers,
> Roger
--
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]