View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0010273 | 10000-014: PubSub | Spec | public | 2025-04-07 14:25 | 2025-07-01 15:46 |
| Reporter | Peter Wehrfritz | Assigned To | Matthias Damm | ||
| Priority | normal | Severity | minor | Reproducibility | have not tried |
| Status | assigned | Resolution | open | ||
| Summary | 0010273: 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. | ||||
| Tags | No tags attached. | ||||
| Commit Version | 1.05.06 | ||||
| Fix Due Date | 2025-09-15 | ||||
|
|
Discussed in meeting today - for the broker case the address makes no sense since the messages may be forwarded to different brokers and Publisher may be completly different than Subscriber address. We should change UADP to exclude the address for the broker transport case. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2025-04-07 14:25 | Peter Wehrfritz | New Issue | |
| 2025-05-13 16:36 | Jim Luth | Assigned To | => Matthias Damm |
| 2025-05-13 16:36 | Jim Luth | Status | new => assigned |
| 2025-05-13 16:37 | Jim Luth | Commit Version | => 1.05.06 RC1 |
| 2025-05-13 16:37 | Jim Luth | Fix Due Date | => 2025-05-31 |
| 2025-07-01 15:43 | Matthias Damm | Note Added: 0023054 | |
| 2025-07-01 15:43 | Matthias Damm | Note Edited: 0023054 | |
| 2025-07-01 15:46 | Jim Luth | Commit Version | 1.05.06 RC1 => 1.05.06 |
| 2025-07-01 15:46 | Jim Luth | Fix Due Date | 2025-05-31 => 2025-09-15 |
