View Issue Details

IDProjectCategoryView StatusLast Update
000548810000-014: PubSubSpecpublic2022-12-08 16:18
ReporterParth Rawal Assigned ToRandy Armstrong  
PrioritynormalSeverityfeatureReproducibilityhave not tried
Status closedResolutionwon't fix 
Summary0005488: UDP with JSON encoding
Description

Currently as per the specification, for UDP communication using PubSub, only UDP with UADP transport profile URI has been specified. It would make sense also to add UDP with JSON encoding, since UDP is the fastest and JSON is very easy to decode.

TagsNo tags attached.
Commit Version
Fix Due Date

Activities

Randy Armstrong

2021-06-09 14:18

administrator   ~0014531

There is no mechanism for chunking JSON messages. This has to be added to Part 14 before a UDP mapping would be practical.

Randy Armstrong

2021-06-09 14:25

administrator   ~0014532

Note that the primary use case for JSON is to allow non-UA aware consumers and/or producers. This means they will not understand chunked JSON.

So it is not clear why this is useful/needed.

Jim Luth

2022-12-08 16:18

administrator   ~0018277

No demand for this combination and too much work to complete.

Issue History

Date Modified Username Field Change
2020-02-28 09:12 Parth Rawal New Issue
2020-05-19 17:15 Jim Luth Assigned To => Randy Armstrong
2020-05-19 17:15 Jim Luth Status new => assigned
2021-06-09 14:18 Randy Armstrong Status assigned => acknowledged
2021-06-09 14:18 Randy Armstrong Note Added: 0014531
2021-06-09 14:25 Randy Armstrong Note Added: 0014532
2021-06-09 14:25 Jim Luth Project 10000-007: Profiles => 10000-014: PubSub
2022-12-08 16:18 Jim Luth Status acknowledged => closed
2022-12-08 16:18 Jim Luth Resolution open => won't fix
2022-12-08 16:18 Jim Luth Note Added: 0018277