Skip to content
This repository has been archived by the owner on Nov 16, 2021. It is now read-only.

RFC-229 MQTT Wildcard topics #34

Open
bjhargrave opened this issue Jan 20, 2017 · 2 comments
Open

RFC-229 MQTT Wildcard topics #34

bjhargrave opened this issue Jan 20, 2017 · 2 comments
Assignees
Labels
publiccomment Public comment

Comments

@bjhargrave
Copy link
Member

Original bug ID: BZ#207
From: Dmytro Pishchukhin <dmytro.pishchukhin@gmail.com>
Reported version: unspecified

@bjhargrave
Copy link
Member Author

Comment author: Dmytro Pishchukhin <dmytro.pishchukhin@gmail.com>

In case of topic wildcards we loose topic details in a subscription PushStream, because it contains only payload.

Example:
subscribe to topic PUB/SENSORS/+/TEMP (single level wildcard is for sensor IDs). In this case, it's required to process payload with topic to map temp value to specific sensor ID.

@bjhargrave
Copy link
Member Author

Comment author: @tverbele

You are right ... we will need a MQTTMessage type with a topic String and payload ByteBuffer for the PushStream. I will update the RFC as such

@bjhargrave bjhargrave added the publiccomment Public comment label May 1, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
publiccomment Public comment
Projects
None yet
Development

No branches or pull requests

2 participants