View Issue Details

IDProjectCategoryView StatusLast Update
001027310000-014: PubSubSpecpublic2025-04-07 14:25
ReporterPeter Wehrfritz Assigned To 
PrioritynormalSeverityminorReproducibilityhave not tried
Status newResolutionopen 
Summary0010273: Inconsistency between Json and Uadp PubSubConnection discovery messages
Description

For PubSubConnection discovery messages encoded with Json, the Address of the connection shall be empty, whereas with Uadp the address should be transmitted. So on a MQTT broker you can get the configured address via Uadp, but not with Json. What's the rational behind that? It would be much easier to implement if the address was treated the same (present or empty) regardless of the encoding and transport layer.

TagsNo tags attached.
Commit Version
Fix Due Date

Activities

There are no notes attached to this issue.

Issue History

Date Modified Username Field Change
2025-04-07 14:25 Peter Wehrfritz New Issue