Assembly: RFA8_NET110_x64 (in RFA8_NET110_x64.dll) Version: 220.127.116.11
Primitive data types include value types such as UInt and Int. Primitive data types also include simple interfaces such as Real, Date, Time, DateTime, etc.
DataBuffer properties support limited conversions between related types such as Int, UInt, and Real. For example, if a dataBuffer object contains an Int encoded value, then the get accessor for Real property will return a Real value which is equal to an Int value returned by the get accessor for Int property.
1) Conversions from signed to unsigned values will loose the sign.
2) Variables will be truncated if they are converted from 8-byte to 4-byte values.
A DataBuffer within a nesting layer may contain only primitive data types and simple non-Data interfaces.
The DataBufferEnum and DataBufferEncodedEnum values are unique and independent of each other.
DataBuffer is designed for efficient encoding and decoding. It is not optimized for caching with respect to object size or data lifecycle. If caching is necessary, the values stored by these objects should be extracted and copied into application cache objects and primitives.
Due to encoding optimizations, if a DataBuffer "Set" method or the set accessor of properties is called, the value may not be available via a "Get" method or the get accessor of properties. The "Set" methods or the set accessor just store the values and do not necessarily encocde the value into wire format. The value is encoded when the DataBuffer is passed to a WriteIterator or when the containing Msg is passed in to the RFA SessionLayer. The value will only be available when the DataBuffer is decoded by the receiving application.