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] Updated: (MQTT-63) Is the topic string specified by a publisher immutable


     [ http://tools.oasis-open.org/issues/browse/MQTT-63?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Andrew Banks updated MQTT-63:
-----------------------------

    Proposal: The subscriber receives a message containing a topic name which is the same as the one used by the publisher. It is not necessarily the same as the Topic Filter used by the subscriber because the Topic Filter might contain wild card characters.  (was: "When received by a client that subscribed using wildcard characters, this string is the absolute topic that matched the wildcard subscription.")

> Is the topic string specified by a publisher immutable
> ------------------------------------------------------
>
>                 Key: MQTT-63
>                 URL: http://tools.oasis-open.org/issues/browse/MQTT-63
>             Project: OASIS Message Queuing Telemetry Transport (MQTT) TC
>          Issue Type: Improvement
>          Components: core
>            Reporter: Allan Stockdill-Mander 
>
> Under "Topic Name" for the PUBLISH packet there is currently a line that says "When received by a client that subscribed using wildcard characters, this string is the absolute topic specified by the originating publisher and not the subscription string used by the client." By saying "originating publisher" it excludes scenarios.
> Is this really intended as some current implementations such as RSMB do manipulate the topic string, for example with mountpoints a publish or subscribe topic string can have the mountpoint prepended.
> Equally a server may want to route between different topics, for example linking /a and /b such that a publish to /a is replicated to /b. If a client has subscribed to /b it would make more sense that the topic string in the PUBLISH it receives is /b rather than the originating PUBLISH's /a.

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