SerializerFlags
Description
Flags for controlling the binary layout that used by ISerializer objects.
The documentation of the individual flags describes how the binary layout changes for the methods that write values. Although not mentioned explicitly, the same changes apply to the corresponding read methods.
- See also
Public / Constants
UseVarIntForLength
Use IByteWriter.WriteVarInt32 when writing length values with ISerializer.WriteLength, instead of IBinaryWriter.WriteInt32?
UseUnsignedLength
If UseVarIntForLength is present, use IByteWriter.WriteVarUInt32 instead of IByteWriter.WriteVarInt32, when writing length values with ISerializer.WriteLength?
UseUtf8ForString
Shall the ISerializer.WriteString method write a length-prefixed sequence of UTF-8 code units, instead of a length-prefixed sequence of UTF-16 code units (or ISO-8859-1 code units, if possible)?
UsePlainObjectGuids
Shall the ISerializer.WriteObject method emit GUID values in plain text form (36 bytes), instead of GUID.First and GUID.Second (16 bytes).
UseVarIntForValues
Use IByteWriter.WriteVarInt32 when writing integral values with IByteWriter.WriteInt8, IBinaryWriter.WriteInt16, IBinaryWriter.WriteInt32 and IByteWriter.WriteVarInt64 when writing integral values with IBinaryWriter.WriteInt64?
UseUnsignedValues
If UseVarIntForValues is present, use IByteWriter.WriteVarUInt32 and IByteWriter.WriteVarUInt64 instead of their signed counterparts, when writing integral values?
UseNoShortcutCode
If UseNoShortcutCode is present, the IByteReader.ReadVarInt64, IByteReader.ReadVarUInt64, IByteWriter.WriteVarInt64 and IByteWriter.WriteVarUInt64 methods do not use shortcut coding (which yields between 1 and 10 bytes). Otherwise, they do (which yields between 1 and 9 bytes).