Additional operator

, ,
1

Imported from previous forum

2

Would it be possible to consider the following operators in a template:
‘equal - n’ - for introducing synonymous values in messages that are always true, where n is tag. This will facilitate ability to rethrieve data by different means. e.g. Symbol - tag 55, when represents exchange code and SecurityIDSource - tag 22 = 8 - Exchange Symbol and SecurityID - tag 48 matches value in tag 55. This will allow to send over the wire only one of them (48 and derive 55 from 48), operator would be ‘equal 48’. Today, I would need to use different templates.
‘substr:n(k-k+i)’ - for values that are substrings of a larger value, where n is a tag, k is start position and k+i is end position. e.g. if a value is a preffix, suffix or anything in between.
I thank you in advance.

3

I’m not sure I fully understand your proposal but it looks that you want to utilize some inter-field affinity. If this is the case, it is to some extent already possible through the use of the key attribute in the template:

key="SymbolCommonKey"

Would it be possible to consider the following operators in a template:
‘equal - n’ - for introducing synonymous values in messages that are
always true, where n is tag. This will facilitate ability to rethrieve
data by different means. e.g. Symbol - tag 55, when represents exchange
code and SecurityIDSource - tag 22 = 8 - Exchange Symbol and SecurityID

  • tag 48 matches value in tag 55. This will allow to send over the wire
    only one of them (48 and derive 55 from 48), operator would be ‘equal
    48’. Today, I would need to use different templates. ‘substr:n(k-k+i)’ -
    for values that are substrings of a larger value, where n is a tag, k is
    start position and k+i is end position. e.g. if a value is a preffix,
    suffix or anything in between. I thank you in advance.
4

[Slippery keyboard … :slight_smile: Here’s the full version]

I’m not sure I fully understand your proposal but it looks that you
want to utilize some inter-field affinity. If this is the case, it is
to some extent already possible through the use of the key attribute in
the template:

In your data model you’d still have two fields to read (and perhaps populate depending on the layering in your encoding application), but on the wire only one instance would be present in the stream if the two fields were indeed equal.

You can use key with the delta operator too if you want to compress fields that share common prefixes or suffixes.

/David

Would it be possible to consider the following operators in a
template: ‘equal - n’ - for introducing synonymous values in messages
that are always true, where n is tag. This will facilitate ability to
rethrieve data by different means. e.g. Symbol - tag 55, when
represents exchange code and SecurityIDSource - tag 22 = 8 - Exchange
Symbol and SecurityID

  • tag 48 matches value in tag 55. This will allow to send over the
    wire only one of them (48 and derive 55 from 48), operator would be
    ‘equal 48’. Today, I would need to use different templates. ‘substr:n(k-
    k+i)’ - for values that are substrings of a larger value, where n is
    a tag, k is start position and k+i is end position. e.g. if a value
    is a preffix, suffix or anything in between. I thank you in advance.