View Issue Details

Jump to NotesJump to History
IDProjectCategoryView StatusDate SubmittedLast Update
000266710000-011: Historical AccessSpecpublic2013-11-08 16:222015-06-23 15:50
ReporterMatthias Damm Assigned ToRod Stein  
PrioritynormalSeverityminorReproducibilityalways
Status closedResolutionfixed 
Target Version1.03Fixed in Version1.03 
Summary0002667: Description of Continuation Point (6.3) does not match general concept
Description

OPC UA has the concept of a max size list of continuation points per session. As long as the max size is not exceeded, the continuation points stay valid as long they are not used by the client. A server may in addition time out continuation points.

Part 11 - 6.3 Continuation Points - defines
If the Client specifies a ContinuationPoint that does not correspond with last returned ContinuationPoint from the Server, then the Server shall return a Bad_ContinuationPointInvalid error.

This sentence is wrong. This would make parallel execution of HistorRead calls for different nodes impossible.

The sentence must be changed to:
If the Client specifies a ContinuationPoint that is not longer valid, then the Server shall return a Bad_ContinuationPointInvalid error.

TagsNo tags attached.
Commit Version
Fix Due Date

Activities

Rod Stein

2015-05-25 19:02

developer   ~0006079

Fixed in 1.03 draft 03
Removed the part of the sentence suggested and made it "is no longer valid" to match with how continuation points work in the rest of the specifications.

Jim Luth

2015-06-23 15:50

administrator   ~0006170

Agreed to changes in telecon.

Issue History

Date Modified Username Field Change
2013-11-08 16:22 Matthias Damm New Issue
2013-11-12 17:12 Jim Luth Status new => assigned
2013-11-12 17:12 Jim Luth Assigned To => Rod Stein
2014-08-19 17:36 Jim Luth Category (No Category) => Spec
2014-08-19 17:37 Jim Luth Target Version => 1.03
2015-05-25 19:02 Rod Stein Note Added: 0006079
2015-05-25 19:02 Rod Stein Status assigned => resolved
2015-05-25 19:02 Rod Stein Resolution open => fixed
2015-06-23 15:50 Jim Luth Note Added: 0006170
2015-06-23 15:50 Jim Luth Status resolved => closed
2015-06-23 15:50 Jim Luth Fixed in Version => 1.03