OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

mqtt message

[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=34126#action_34126 ] 

Allan Stockdill-Mander  commented on MQTT-42:

I'm not sure my previous comment is particularly clear at making the point I was intending. Prior to V3.1 client id was the only protocol field available to identify a client, 3.1 introducing the username and password fields. Given that (and it's explicitly allowed to connect with a username and no password) it's perhaps more appropriate to think of client id as a session id instead.
If you don't care about the persistence of your session (cleansession true) why would you care about knowing your session id?
Equally in a future revision making it session id strongly supports the case of the server autogenerating an id and communicating it back to the client.

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