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

User properties implementation #876

Closed
Tracked by #695
andsel opened this issue Nov 27, 2024 · 0 comments · Fixed by #877
Closed
Tracked by #695

User properties implementation #876

andsel opened this issue Nov 27, 2024 · 0 comments · Fixed by #877
Labels

Comments

@andsel
Copy link
Collaborator

andsel commented Nov 27, 2024

Abstract

Most packets has User Properties. User properties on PUBLISH are included with the message and are defined by the Client applications. The user properties on PUBLISH and Will Properties are forwarded by the Server to the receiver of the message. User properties on the CONNECT, SUBSCRIBE, and UNSUBSCRIBE packets are defined by the Server implementation. The user properties on CONNACK PUBACK, PUBREC, PUBREL, PUBCOMP, SUBACK, UNSUBACK and AUTH packets are defined by the sender, and are unique to the sender implementation. The meaning of user properties is not defined by MQTT.

Implementation

This implementation focus on implementing user properties for just the PUBLISH and Will message. These properties will be forwarded to the subscribers.
All other user properties are not considered because at the moment the server implementation doesn't define any specification for these. If in a future a use case came up, will be considered.

@andsel andsel changed the title User properties: Add User Properties to most packets. User properties on PUBLISH are included with the message and are defined by the Client applications. The user properties on PUBLISH and Will Properties are forwarded by the Server to the receiver of the message. User properties on the CONNECT, SUBSCRIBE, and UNSUBSCRIBE packets are defined by the Server implementation. The user properties on CONNACK PUBACK, PUBREC, PUBREL, PUBCOMP, SUBACK, UNSUBACK and AUTH packets are defined by the sender, and are unique to the sender implementation. The meaning of user properties is not defined by MQTT. User properties implementation Nov 27, 2024
@andsel andsel added the mqtt5 label Nov 27, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant