Add runtime configuration setting for plane XML and JSON encodings
Submitted by Gyorgy Rethy
Link to original bug (#499410)
Description
Today Titan encodes values in XML in a "nice formatting" way, i.e. inserting \n\t characters between elements. On the other hand values in JSON are encoded in "plane" mode, i.e. no formatting characters are inserted.
- The formatting of encoded values should be unified;
- in some cases, e.g. in low bandwidth IoT connections, superfluous characters are not desirable;
- in cases the user wants to process the received (or to be sent) encoded strings in TTCN-3, its formatting useful be known beforehand.
Therefore it is proposed to introduce a new runtime parameter to control formatting for XML and JSON encodings (maybe aso for TEXT?) with the proposed values: PLANESEND | PLANERCV | FORMATTEDSEND | FORMATTEDRCV | ASRECEIVED (this would have effect on the decoder only)
Version: 5.5.0