View Issue Details

Jump to NotesJump to History
IDProjectCategoryView StatusDate SubmittedLast Update
000995810000-014: PubSubSpecpublic2024-10-17 14:272025-03-10 21:46
ReporterJim Luth Assigned ToMatthias Damm  
PrioritynormalSeverityminorReproducibilityalways
Status resolvedResolutionfixed 
Product Version1.05.04 RC1 
Fixed in Version1.05.06 RC1 
Summary0009958: Clarify legal values for PublishingInterval
Description

Publishing interval is defined as a Duration but the spec does not disallow any values.

Are negative values allowed? (I suspect not, but this should be explicitly stated)

Is zero allowed? (If so, it should work like Client/Server to mean "as fast as possible". Also make sure if it is 0, all the things that are multiples of PublishingInterval e.g. KeepAlivePeriod still make sense.)

TagsNo tags attached.
Commit Version1.05.06 RC1
Fix Due Date2025-03-15

Activities

Matthias Damm

2025-01-15 08:21

developer   ~0022282

Negative values make no sense.
A value of 0 is valid if the application is able to handle it (e.g. events or data on application specific trigger). The other time intervals like keep alive are absolute values and are independent of the PublishingInterval (this is different than in client/server)

Matthias Damm

2025-03-10 21:46

developer   ~0022505

6.2.6.2 PublishingInterval
Added
Negative value are invalid. If the PublishingInterval is 0, the KeyFrameCount of all DataSetWriters in the WriterGroup shall be 0.

6.2.6.3 KeepAliveTime
Added that KeepAliveTime shall be larger than 0.

Issue History

Date Modified Username Field Change
2024-10-17 14:27 Jim Luth New Issue
2024-10-17 14:28 Jim Luth Description Updated
2025-01-09 14:58 Jim Luth Assigned To => Matthias Damm
2025-01-09 14:58 Jim Luth Status new => assigned
2025-01-09 14:58 Jim Luth Assigned To Matthias Damm =>
2025-01-09 14:58 Jim Luth Status assigned => new
2025-01-14 16:46 Jim Luth Assigned To => Matthias Damm
2025-01-14 16:46 Jim Luth Status new => assigned
2025-01-14 16:47 Jim Luth Commit Version => 1.05.06 RC1
2025-01-14 16:47 Jim Luth Fix Due Date => 2025-03-15
2025-01-15 08:21 Matthias Damm Note Added: 0022282
2025-03-10 21:46 Matthias Damm Status assigned => resolved
2025-03-10 21:46 Matthias Damm Resolution open => fixed
2025-03-10 21:46 Matthias Damm Fixed in Version => 1.05.06 RC1
2025-03-10 21:46 Matthias Damm Note Added: 0022505