DecoderOptions contains the following:
JSON key: "name"
key | Required? | Type | Value description |
|---|---|---|---|
Name | Yes | String | A string representing the name of the decoder as it will appear in decoded output and elsewhere in VMX-Capture configuration. |
DecoderOptions example:
"DecoderOptions" : { "Name":"utp_line", },DecoderOptions Name output:
utp_line.Version=49;utp_line.Cat=81;utp_line.Type=76;utp_line.Orig=UU;utp_line.Timestamp=20200808T143251.584959461;utp_line.Timestamp_raw=1596897171584959461;utp_line.Sequence=11;utp_line.Token=8352293JSON key: "flags"
key | Required? | Type | Value description |
|---|---|---|---|
flags | Yes | Array | A JSON array of CSV values, passing additional options to the decoder. |
DecoderOptions example:
"DecoderOptions" : { "flags" : ["multiple_messages"] },The supported flags are:
multiple_messages
gap_detection
flag: multiple_messages
A packet header is only decoded once. This flag tells the decoder to repeatedly decode messages until packet data runs out. One message is a MessageHeader and one message is payload.
Required for protocols like Currenex ITCH which has delimiters per message.
flag: gap_detection
This tells the decoder to initialise additional message statistics. To ensure gap detection works correctly, you should also specify the "seq_num" flag on a datafield which is of type "uint".