OASIS Message Queuing Telemetry Transport (MQTT) TCIcon indicating the project type

OASIS Message Queuing Telemetry Transport (MQTT) TC

Uploaded image for project: 'OASIS Message Queuing Telemetry Transport (MQTT) TC'
  1. OASIS Message Queuing Telemetry Transport (MQTT) TC
  2. MQTT-415

Is there any order to Server References?

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: 5, wd11
    • Fix Version/s: 5, wd12
    • Component/s: core
    • Labels:
      None

      Description

      3304 The Server Reference is a UTF-8 Encoded String. The value of this string is a space separated list of
      3305 references. The format of references is not specified here.

      Is there any order to the list of references if the client chooses to observe the hint? For example, is the list in priority order or can the client pick an arbitrary reference? Is there any guidance that we want to provide in this case?

        Attachments

          Activity

          Ascending order - Click to sort in descending order
          Hide
          Permalink
          ragupta2 Rahul Gupta (Inactive) added a comment - - edited

          I remember a similar question was brought up earlier and my understanding was that we want to leave this up to the different implementations to decide. However I agree that non normative guidance could be provided to help the implementers.

          Show
          ragupta2 Rahul Gupta (Inactive) added a comment - - edited I remember a similar question was brought up earlier and my understanding was that we want to leave this up to the different implementations to decide. However I agree that non normative guidance could be provided to help the implementers.
          Hide
          Permalink
          ken.borgendale Ken Borgendale (Inactive) added a comment -

          The discussion on thus subject broke down when we tried to specify the contents of the reference or the semantics of using them. We only reached agreement by saying that the field exists and that it could represent a set of references. As we do not even say what the client does with one of these references, it is not clear that we can say much about what the client does with multiple of them.

          If we think some non-normative text could be useful here, I would say that the reference is meant to identify a server to connect to, and if multiple are specified then the client is meant to choose one of them.

          Show
          ken.borgendale Ken Borgendale (Inactive) added a comment - The discussion on thus subject broke down when we tried to specify the contents of the reference or the semantics of using them. We only reached agreement by saying that the field exists and that it could represent a set of references. As we do not even say what the client does with one of these references, it is not clear that we can say much about what the client does with multiple of them. If we think some non-normative text could be useful here, I would say that the reference is meant to identify a server to connect to, and if multiple are specified then the client is meant to choose one of them.
          Hide
          Permalink
          ken.borgendale Ken Borgendale (Inactive) added a comment -

          Add non-normative text and references as required.

          Show
          ken.borgendale Ken Borgendale (Inactive) added a comment - Add non-normative text and references as required.
          Hide
          Permalink
          ken.borgendale Ken Borgendale (Inactive) added a comment -

          Issue included in MQTTv5.0 CS01 December 25, 2017

          Show
          ken.borgendale Ken Borgendale (Inactive) added a comment - Issue included in MQTTv5.0 CS01 December 25, 2017

            People

            • Assignee:
              ken.borgendale Ken Borgendale (Inactive)
              Reporter:
              brianraymor Brian Raymor [X] (Inactive)
            • Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: