Skip to content

Do not require priority for publish messages#318

Merged
sophokles73 merged 2 commits intoeclipse-uprotocol:mainfrom
etas-contrib:do_not_require_priority_for_publish_messages
Jan 12, 2026
Merged

Do not require priority for publish messages#318
sophokles73 merged 2 commits intoeclipse-uprotocol:mainfrom
etas-contrib:do_not_require_priority_for_publish_messages

Conversation

@sophokles73
Copy link
Copy Markdown
Contributor

Updated UAttributes specification to make the 'priority' attribute
optional for publish messages. This change can help reduce the size of
encoded publish messages by allowing producers to omit the priority
setting when not necessary.

Fixes #315

Updated UAttributes specification to make the 'priority' attribute
optional for publish messages. This change can help reduce the size of
encoded publish messages by allowing producers to omit the priority
setting when not necessary.

Fixes eclipse-uprotocol#315
@sophokles73 sophokles73 added the bug Something isn't working label Jan 2, 2026
@sophokles73
Copy link
Copy Markdown
Contributor Author

@PLeVasseur would you mind taking a look?

Copy link
Copy Markdown
Contributor

@PLeVasseur PLeVasseur left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good overall.

Approving assuming that the rewords / unification / nits make sense.

Comment thread basics/upriority.adoc Outdated
Comment thread basics/upriority.adoc Outdated
Comment thread up-l1/mqtt_5.adoc Outdated
@sophokles73 sophokles73 force-pushed the do_not_require_priority_for_publish_messages branch from 98bb51d to 0e8e23e Compare January 12, 2026 07:12
@sophokles73 sophokles73 merged commit f3ff839 into eclipse-uprotocol:main Jan 12, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug Something isn't working

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Publish messages should not be required to have priority level set explicitly

2 participants