View Issue Details

IDProjectCategoryView StatusLast Update
000568510000-003: Address SpaceSpecpublic2024-03-26 16:22
ReporterDavid Levine Assigned ToJeff Harding  
PrioritynormalSeveritymajorReproducibilityhave not tried
Status closedResolutionfixed 
Fixed in Version1.05.04 RC1 
Summary0005685: Define data sets for use in TCP Binary
Description

Goal: create a data contract between client-server so that a client knows what each message will contain.

The spec imposes few constraints on the data types and sizes a server can send to a client; the data can be unbounded.
For example, a Variable node's Data Type, ValueRank and ArrayDimensions may be set to an array of unknown size of a Variant (BaseDataType, i=24). This makes it impossible for a client to determine how big the data will be per transmitted value, so it cannot determine the upper bound on processing time.

Use the same concepts from pub-sub with tcp binary so that the server sends data sets and the client knows the type and size of each value.

TagsNo tags attached.
Commit Version1.05.04 RC
Fix Due Date2024-02-01

Activities

Jim Luth

2020-08-25 16:32

administrator   ~0012723

May be solved with a TCP binding to pub/sub.

Jim Luth

2024-01-02 17:31

administrator   ~0020557

Agreed to describe best practices for Servers to restrict this metadata to the most restrictive values possible.

David Levine

2024-01-04 11:04

developer   ~0020570

Suggested guidance:

To maximize interoperability with Clients, when a Server instantiates Variable Nodes the DataType, ValueRank and ArrayDimension attributes should be set to the most restrictive values for the instance. For example, if a Variable Node will produce a 1-dimension array of floats with a maximum array length of 10, set DataType = Float, ValueRank = 1, ArrayDimensions = [10]. If the array length has no fixed upper limit, then set ArrayDimensions = [0], [] (empty array) or NULL.

Jeff Harding

2024-03-14 16:21

developer   ~0020899

Added suggested guidance statement to 5.6.2.

Jim Luth

2024-03-26 16:22

administrator   ~0021029

Agreed to changes edited in Web meeting.

Issue History

Date Modified Username Field Change
2020-06-04 13:50 David Levine New Issue
2020-08-25 16:32 Jim Luth Note Added: 0012723
2020-08-25 16:32 Jim Luth Status new => acknowledged
2024-01-02 17:31 Jim Luth Note Added: 0020557
2024-01-02 17:31 Jim Luth Project Feature Requests => 10000-003: Address Space
2024-01-02 17:31 Jim Luth Category Feature Request => Api Change
2024-01-02 17:31 Jim Luth Assigned To => Jeff Harding
2024-01-02 17:31 Jim Luth Status acknowledged => assigned
2024-01-02 17:32 Jim Luth Category Api Change => Spec
2024-01-02 17:32 Jim Luth Commit Version => 1.05.04 RC
2024-01-02 17:32 Jim Luth Fix Due Date => 2024-02-01
2024-01-04 11:04 David Levine Note Added: 0020570
2024-03-14 16:21 Jeff Harding Status assigned => resolved
2024-03-14 16:21 Jeff Harding Resolution open => fixed
2024-03-14 16:21 Jeff Harding Fixed in Version => 1.05.04 RC1
2024-03-14 16:21 Jeff Harding Note Added: 0020899
2024-03-26 16:22 Jim Luth Status resolved => closed
2024-03-26 16:22 Jim Luth Note Added: 0021029