Skip to content
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

[Feature] Independent payload and topic per connection #886

Open
000xiaoxiao000 opened this issue Feb 9, 2022 · 4 comments
Open

[Feature] Independent payload and topic per connection #886

000xiaoxiao000 opened this issue Feb 9, 2022 · 4 comments
Assignees
Labels
desktop MQTTX Desktop discussion This issues and pr are worth discussing feature This pr is a feature

Comments

@000xiaoxiao000
Copy link

Motivation

Payload follows individual topic.

Detailed design

When multiple messages are created, the payload changes,

The payload of A is $v1/123/ POST, and the payload of B is $v1/456/ POST. The payload of A is the payload of A. The payload of B is the payload of B .

@000xiaoxiao000 000xiaoxiao000 added the feature This pr is a feature label Feb 9, 2022
@ysfscream ysfscream added the discussion This issues and pr are worth discussing label Feb 10, 2022
@oceanlvr
Copy link
Contributor

@000xiaoxiao000 Good idea!
Maybe we should reflect on what kind of historical message settings are reasonable. We can make historical news

  1. History messages are followed by the connection's send history.
  2. History messages are more with the send history. (current)
  3. History messages are sent history with the current topic. (you expect)

maybe we could review this design.

@000xiaoxiao000
Copy link
Author

000xiaoxiao000 commented Feb 10, 2022

image
image

@ysfscream
Copy link
Member

@000xiaoxiao000 Thanks for your feedback. I understand what you mean by the screenshot, I think the payload and topic of each connection should be independent, similar to IM software where each chat message should be different, right?

@000xiaoxiao000
Copy link
Author

@000xiaoxiao000感谢您的反馈。我明白你的截图是什么意思,我认为每个连接的payload和topic应该是独立的,类似于IM软件,每个聊天消息应该不同,对吧?

yes.

@ysfscream ysfscream changed the title [Feature] the title of Feature_Want report [Feature] Independent payload subject per connection Feb 14, 2022
@ysfscream ysfscream changed the title [Feature] Independent payload subject per connection [Feature] Independent payload and topic per connection Feb 14, 2022
@ysfscream ysfscream assigned ysfscream and unassigned oceanlvr Jul 14, 2023
@ysfscream ysfscream added the desktop MQTTX Desktop label Jul 14, 2023
@ysfscream ysfscream added this to the v2.0.0-beta.1 milestone Sep 1, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
desktop MQTTX Desktop discussion This issues and pr are worth discussing feature This pr is a feature
Projects
Status: Backlog
Development

No branches or pull requests

3 participants