[This message was posted by Mikael Brannstrom of Nordic Growth Market
<[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/1b5a520c - PLEASE DO NOT REPLY BY MAIL.]
<uInt32 name="TheField" id="123" presence="optional"/>
The default value for the 'presence' attribute is 'mandatory'. This is the
template syntax in FAST 1.1.
Hanno is correct that when sending TheField=null it is actually sent as 0
(zero) and TheField=1 would mean that the value 2 is sent over the wire.
/Mikael
> If I am not mistaken, zero is the NULL value and all "real" integers are
> shifted by one, i.e. 0 is 1, 1 is 2 etc. on the wire. The decoder then needs
> to subtract 1 to provide the real value to the application. Zeor on the wire
> then represents the NULL value and can be given to the application in
> whatever way it expects to see NULL values.
>
> > I knwo this is probably a ver simple question BUT how is a UInt32 field
> > defined as having null support in the template defination?
[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.
