0002887: Continuation point handling for large HistoryRead requests

ID	Project	Category	View Status	Date Submitted	Last Update

0002887	10000-011: Historical Access	Spec	public	2014-11-17 21:31	2015-08-18 15:27

Reporter	Matthias Damm	Assigned To	Rod Stein
Priority	normal	Severity	minor	Reproducibility	always
Status	closed	Resolution	fixed
Product Version	1.02
Target Version	1.03	Fixed in Version	1.03

Summary	0002887: 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.
Tags	No tags attached.

Commit Version
Fix Due Date

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

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.