-
Notifications
You must be signed in to change notification settings - Fork 81
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add support for placeholders in topic #5
Comments
Will #6 work for your use case? |
@licensedslacker can you describe the suggestion with topic placeholders in more detail? How about just letting each client sending to their own topic (what you suggest as example)? If brokers treat topics with different number of writers or messages in the queue differently it may skew the measurements. |
I think case #6 does not directly satisfy my request. My intention was to add a unique client ID to the topic, not just a random number. The use case what I had in my mind was many-to-one topology where multiple clients produce messages to one receiver and the sender information is encoded into the topic. |
Sorry for the late reply. Even if there are some similarities, my proposal is slightly different from the one of @licensedslacker . This allows a user to test the impact of the number of different topics to the broker. Think about having 100 fixed clients and you want to see what happen when there are 10, 20, 50 or 100 possible topics. A special case, is when N == M (clients == different topics you want to use). Here we are in the case proposed by @licensedslacker , because we can reuse the topic fashion he explained in the first post. |
It would be handy to have placeholders in the topic field.
For example "/topic/%i" become "/topic/1" when connected by a client with ID 1.
Client ID would be one field. A random unique number would be also nice.
The text was updated successfully, but these errors were encountered: