yongjhih/rx-mqtt

Access to precise topic when message is delivered

Open

#2 opened on Oct 10, 2017

View on GitHub
 (2 comments) (0 reactions) (0 assignees)Java (4 forks)github user discovery
enhancementhelp wanted

Repository metrics

Stars
 (18 stars)
PR merge metrics
 (PR metrics pending)

Description

In scenarios when subscription is made to a wildcard topic (e.g. "myorg/test/#") client needs to get the precise topic URI too. E.g. when publisher sends "myorg/test/dream/true" the subscriber needs to get the full topic, not only the payload. When no wildcards are used the subscribed topic is equal to the received one. But when wildcards come into play some information is lost - the suffux in the example above. Is there a possiblity to add the topic to emitted data? Or it is a design decision that does not fit with "wildcard" concept?

Looking over the code, it seems that the variable "String topic2" in messageArrived() function is not forwarded on emitting - in my case it contains the actual topic "myorg/test/dream/true" as delivered by Paho.

Contributor guide

Research direction
Locate the messageArrived function and modify the emitted data to include the precise topic string (topic2) instead of or in addition to the payload.
Tech stack
java
Domain
backend
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
JavaGit
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
85