Details

    • Type: Improvement
    • Status: Closed
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: 3.1.1
    • Fix Version/s: 3.1.1
    • Component/s: core
    • Labels:
      None
    • Environment:

      N/A

    • Proposal:
      Hide

      Non-normative:
      A client implementation may provide a convenience method to generate a random Client Identifier. Use of such a method should be actively discouraged when the Clean Session flag is set to 0.

      Show
      Non-normative: A client implementation may provide a convenience method to generate a random Client Identifier. Use of such a method should be actively discouraged when the Clean Session flag is set to 0.

      Description

      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

        Attachments

          Activity

          Hide
          andrew_schofield Andrew Schofield (Inactive) added a comment -

          I agree with the previous comment. Within the scope of the charter, we're not permitted to introduce an incompatible change, such as a special meaning for a zero-length ClientId on the CONNECT packet. I like that idea, but I think we can only go as far as the previous comment in this version of the specification.

          Show
          andrew_schofield Andrew Schofield (Inactive) added a comment - I agree with the previous comment. Within the scope of the charter, we're not permitted to introduce an incompatible change, such as a special meaning for a zero-length ClientId on the CONNECT packet. I like that idea, but I think we can only go as far as the previous comment in this version of the specification.
          Hide
          coppen Richard Coppen (Inactive) added a comment -

          Approved TC Meeting 12.09.2013

          Show
          coppen Richard Coppen (Inactive) added a comment - Approved TC Meeting 12.09.2013
          Hide
          ragupta2 Rahul Gupta (Inactive) added a comment -

          Added the non normative comment in section, 3.1.3.1 Client Identifier

          Show
          ragupta2 Rahul Gupta (Inactive) added a comment - Added the non normative comment in section, 3.1.3.1 Client Identifier
          Hide
          andrew_banks Andrew Banks (Inactive) added a comment -

          Fixed in WD12

          Show
          andrew_banks Andrew Banks (Inactive) added a comment - Fixed in WD12
          Hide
          coppen Richard Coppen (Inactive) added a comment -

          WD12 line 661

          Show
          coppen Richard Coppen (Inactive) added a comment - WD12 line 661

            People

            • Assignee:
              andrew_banks Andrew Banks (Inactive)
              Reporter:
              raphcohn Raphael Cohen (Inactive)
            • Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: