View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0004742 | 10000-020: File Transfer | Spec | public | 2019-04-24 13:03 | 2021-05-04 15:50 |
Reporter | drothe82 | Assigned To | Jeff Harding | ||
Priority | normal | Severity | minor | Reproducibility | have not tried |
Status | closed | Resolution | fixed | ||
Summary | 0004742: MaxByteStringLength for file transfer - inconsistency in spec | ||||
Description | In Part 5, 6.3.2. ServerCapabilitesType it says "The MaxByteStringLength Property indicates the maximum number of bytes in a ByteString supported by Variables of the Server. It also specifies the default maximum size of a FileType Object’s read and write buffers. Servers may override this setting by adding the MaxByteStringLength Property defined in Part 3 to an individual DataVariable or FileType Object." However, the MaxByteStringLength property is not mentioned in the definition of FileType (Part 5, C.2 FileType ) and also not mentioned in the definition of the Object NodeClass, as in Part 3, Table 11. Therefore, it is unclear whether a client should look for this property, at instances of FileType. Easiest solution: Alternative solution: | ||||
Tags | No tags attached. | ||||
Commit Version | |||||
Fix Due Date | |||||
related to | 0002979 | closed | Matthias Damm | 10000-005: Information Model | ServerCapabilitiesType::MaxByteStringLength missing |
has duplicate | 0006808 | closed | Jeff Harding | 10000-020: File Transfer | MaxByteStringLength property missing on FileType |
related to | 0006032 | closed | Jeff Harding | 10000-005: Information Model | MaxByteStringLength for file transfer - inconsistency in spec |
|
Part 5 state "The MaxByteStringLength Property indicates the maximum number of bytes in a ByteString supported by Variables of the Server. It also specifies the default maximum size of a FileType Object’s read and write buffers." which is correct however the following sentence "Servers may override this setting by adding the MaxByteStringLength Property defined in OPC 10000-3 to an individual DataVariable or FileType Object." needs correcting since the standard Property MaxByteStringLength is defined as a standard property of VariableNode. Since FileType is an ObjectType we need to fix something. I agree the solution should be to add a new optional property to the FileType and then fix the text in Part 5 by removing the reference to FileType. |
|
Added new optional Property MaxBufferSize and move some text from Part 5 describing the default buffer size. |
|
Agreed to changes in Virtual F2F. |
Date Modified | Username | Field | Change |
---|---|---|---|
2019-04-24 13:03 | drothe82 | New Issue | |
2019-06-18 15:50 | Jim Luth | Relationship added | related to 0002979 |
2019-06-18 15:51 | Jim Luth | Assigned To | => Jeff Harding |
2019-06-18 15:51 | Jim Luth | Status | new => assigned |
2020-06-17 14:26 | Jeff Harding | Project | 10000-005: Information Model => 10000-020: File Transfer |
2020-09-17 15:01 | Jeff Harding | Note Added: 0012906 | |
2020-09-17 15:05 | Jeff Harding | Issue cloned: 0006032 | |
2020-09-17 15:05 | Jeff Harding | Relationship added | parent of 0006032 |
2020-09-17 15:15 | Jeff Harding | Status | assigned => resolved |
2020-09-17 15:15 | Jeff Harding | Resolution | open => fixed |
2020-09-17 15:15 | Jeff Harding | Fixed in Version | => 1.05 |
2020-09-17 15:15 | Jeff Harding | Note Added: 0012911 | |
2020-09-18 13:49 | Jim Luth | Relationship replaced | related to 0006032 |
2020-09-18 14:04 | Jim Luth | Status | resolved => closed |
2020-09-18 14:04 | Jim Luth | Note Added: 0012946 | |
2021-05-04 15:50 | Jim Luth | Relationship added | related to 0006808 |
2021-05-04 15:50 | Jeff Harding | Relationship replaced | has duplicate 0006808 |