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] (MQTT-264) Broadcast publish

    [ https://issues.oasis-open.org/browse/MQTT-264?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=59753#comment-59753 ] 

Andrew Banks commented on MQTT-264:

I Propose that we use the above approach in the form of a committee note as a means to make progress with issues like :
256 - Message Format indication
249 - Add expiry capabilities to MQTT.

For Issues where we are likely to need per message metadata we will need to make an incompatible change to the Publish packet
in order to carry it, we should address this via a charter change in the longer term:
258 - Add RPC semantics to MQTT
253 - Subscription identification.

> Broadcast publish
> -----------------
>                 Key: MQTT-264
>                 URL: https://issues.oasis-open.org/browse/MQTT-264
>             Project: OASIS Message Queuing Telemetry Transport (MQTT) TC
>          Issue Type: New Feature
>          Components: futures
>    Affects Versions: 3.1.1
>            Reporter: Andrew Schofield
>             Fix For: 3.1.1
> One of the proposals for message format indications suggests a kind of convention using a parallel metadata topic tree. For example, a retained message on topic "$META/Fruit/Apples" could be used to indicate the format of messages on topic "Fruit/Apples". A client wishing to publish or subscribe on "Fruit/Apples" could first make a subscription on "$META/Fruit/Apples" to discover the message format. Using the existing pub/sub rules is inconvenient in this case.
> If I want to use the same message format information for all fruity topics, I don't want to publish separate messages on each of "$META/Fruit/Apples", "$META/Fruit/Mangoes" and so on. If I publish on "$META/Fruit", it would not be sufficient to subscribe to "$META/Fruit/Apples" to discover the message format. What I want is a way to publish a message for all fruits.
> Another example comes from the IoT domain. Let's say that I have connected lights subscribing to "lights/<light-id>/off" and each light turns off when it receives a message to its topic. If I want to turn off all lights at once, I could define another topic "lights/alloff" and get each light to make a second subscription. Alternatively, I could publish one message to all lights.

This message was sent by Atlassian JIRA

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]