Publish on multiple topics #6
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
krylovsk
reviewed
Oct 13, 2019
This was referenced Oct 13, 2019
|
After giving it another thought, I think implemented as this it can be confusing to the user because of the different combinations of # of clients and the # of topics. Can you describe your use case in more detail? Let's continue this discussion in #5 (will keep PR open for now) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Since analyse how the broker reacts on several publish also on different topics could be interesting, I added the following feature:
With numTopics the number of different topics can be chosen launching mqtt-benchmark. The client will randomly publish on a topic.
The code adds a random number to the current topic, creating a second level (e.g. "/topic/39").