View Issue Details

Jump to NotesJump to History
IDProjectCategoryView StatusDate SubmittedLast Update
000288710000-011: Historical AccessSpecpublic2014-11-17 21:312015-08-18 15:27
ReporterMatthias Damm Assigned ToRod Stein  
PrioritynormalSeverityminorReproducibilityalways
Status closedResolutionfixed 
Product Version1.02 
Target Version1.03Fixed in Version1.03 
Summary0002887: Continuation point handling for large HistoryRead requests
Description

6.4.4.2 Read processed functionality states that a server can return a continuation point can be returned with an empty result list if the timeout is reached. This is also true for other HistoryReadDetails parameters.

Additional Information

The following statement was added to Part 4 to description of 5.10.3 HistoryRead:
In some cases it may take longer than the Client timeout hint to read the data for all nodes to read. Then the Server may return zero results with a continuation point for the affected nodes before the timeout expires. That allows the Server to resume the data acquisition on the next Client read call.

TagsNo tags attached.
Commit Version
Fix Due Date

Relationships

related to 0002805 closedMatthias Damm 10000-004: Services Handling for large HistoryRead requests 

Activities

Rod Stein

2015-08-11 22:43

developer   ~0006299

Fixed in Part 11 1.03 draft 05

Added text allowing continuation points to be returned for each of the read types when processing may take a long time.

Jim Luth

2015-08-18 15:27

administrator   ~0006301

Agreed to changes edited in telecon.

Issue History

Date Modified Username Field Change
2014-11-17 21:31 Matthias Damm New Issue
2014-11-17 21:31 Matthias Damm Status new => assigned
2014-11-17 21:31 Matthias Damm Assigned To => Rod Stein
2014-11-17 21:31 Matthias Damm Relationship added related to 0002805
2015-08-11 22:43 Rod Stein Note Added: 0006299
2015-08-11 22:43 Rod Stein Status assigned => resolved
2015-08-11 22:43 Rod Stein Resolution open => fixed
2015-08-18 15:27 Jim Luth Note Added: 0006301
2015-08-18 15:27 Jim Luth Status resolved => closed
2015-08-18 15:27 Jim Luth Fixed in Version => 1.03