[This message was posted by Rolf Andersson of Pantor Engineering <[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/90adaef8 - PLEASE DO NOT REPLY BY MAIL.]
William, FAST supports optional fields to efficiently support optional fields at the _application_ level. FAST allows you to express using a NULL representation if a field is present from an application perspective. This is unrelated to the physical presence or absence due to field operator optimizations. /Rolf > Sorry i have looked through the docs and the forum but still am not > clear on what optional is supposed to mean. > > If, for example, I have non optional string copy I cache the value and > in the event that the presence map has zero against this field I used > the cached value. > > Is there a difference for a non-optional field? Eg should I have no > cache for a non optional field and set the value to zero/blank when the > presence map has zero against this field. [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 -~----------~----~----~----~------~----~------~--~---
