|
FAST Protocol
< Previous Next >
Nullable Set
Hanno Klein / Deutsche Börse Systems <>
13 Aug 2010 8:10AM ET FAST 1.2 defines nullable sets to behave like integers. Sets can be used for bitmasks to convey multi-value fields in FIX.
I would like to confirm that shifting wire values by +1 for nullable sets is still required even if (in my application) it can never occur that none of the bits is set, i.e. if I only need to convey NULL but never zero to my counterparty.
I believe there is (intentionally) no way to indicate such semantic in my template for the set field as it will only say presence=optional to indicate that it is nullable. This attribute requires me to shift all non-null values by 1, regardless of the values I am actually going to send in the context of my application. I cannot save the decoder from having to subtract 1 from the value first before interpreting it as a bitmask, right?
Thanks,
Hanno.
|
