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=34096#action_34096 ] 

Allan Stockdill-Mander  commented on MQTT-42:
---------------------------------------------

I'd been thinking about this problem/situation and how instead it might solved on the server side. For example a client connecting with clean session false and a 0 length clientId would be saying; "I don't care about my state I just want to connect and send/receive data", in this case the server can handle either assigning it internally a guaranteed unique clientId or managing it in some other way, but the client implementation doesn't need to know/care about the details or attempt to generate a clientId it hopes will be unique.

This is probably a change beyond the scope of the charter, but as it's related to the above I figure it's worth mentioning here.

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