Enumerator for all data types availiable in RODL.
- Unit: uROClasses.pas
|rtBinary||The Binary type is used to pass unstructured binary data between tiers in your application, also a similar custom class|
|rtBoolean||Used to send Boolean values of true or false.|
|rtCurrency||The Currency type is used to pass fixed-point decimal numbers between the tiers of your application.
this maps to the language's "currency" type, which is a 64-bit fixed-point numerical type with 4 significant decimal points.
|rtInt64||64-bit signed integer type (Int64).|
|rtInteger||32-bit signed integer type (Integer).|
|rtString||The "String" data type is used to represent strings of characters.
If you need to send strings while preserving the full 16 bit Unicode character set, define your services to use the WideString or Utf8String types discussed below. In general, Utf8String will be the best option for strings when using .NET on one or both sides of the communication.
In Delphi, this type maps directly to the 8-bit "string" language type.
|rtUTF8String||The Utf8String data type is used to represent strings of characters. As a compromise between the plain "String" data type and WideStrings, Utf8Strings will be serialized as UTF-8 encoded 8 bit strings preserving any Unicode characters, while maintaining a smaller memory footprint than WideStrings.
the String and Utf8Strings data types will be handled identically, and mapped to the "string" language type. It is up to the application's code to treat received strings as UTF-8 encoded and use the RTL functions to convert them back from and to ANSI or WideString, where needed.
|rtWidestring||The WideString data type is used to represent strings of characters. In contrast to the "String" data type, WideStrings will be serialized as true 16 bit strings, preserving any Unicode characters. As a downside, they will consume twice as much space (in the uncompressed message) as normal String types.|