[This message was posted by Hanno Klein of Deutsche Börse Systems <[email protected]> to the "FAST Protocol" discussion forum at http://fixprotocol.org/discuss/46. You can reply to it on-line at http://fixprotocol.org/discuss/read/03b3db5e - PLEASE DO NOT REPLY BY MAIL.]
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. [You can unsubscribe from this discussion group by sending a message to mailto:[email protected]] -- You received this message because you are subscribed to the Google Groups "Financial Information eXchange" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/fix-protocol?hl=en.
