[This message was posted by Nick S of <[email protected]> to the "4.0
Session" discussion forum at http://fixprotocol.org/discuss/12. You can reply
to it on-line at http://fixprotocol.org/discuss/read/a451981c - PLEASE DO NOT
REPLY BY MAIL.]
Some more questions :)
(1)
Are the tag names same across all FIX versions? For e.g., Tag8 would have same
meaning from FIX4.0 till FIXT.1.1?
(2)
Is there any place I can find matrix of mandatory/optional fields, all at one
place across various FIX version, for given tag? Something like following table
(X=Mandatory, O = Optional)
...........FIX4.0, FIX4.1,.....FIXT.1.1
--Login--
Tag8 X, X, X, ....
Tag9 X, X, 0, ....
....
--Logout--
Tag8 X, X, X, ....
Tag9 X, X, 0, ....
....
(3)
If a tag is mandatory in lower FIX version, can I safely assume, its mandatory
in higher versions as well?
(4)
Can FIX application decide when to initiate Session Disconnect? Or it can be
left to the session layer (which does every 24 hrs)?
In other words, can FIX application have only 2 function interface towards FIX
session
FIX Application --> {SendFixMsg(), ReceiveFixMsg()}-->FIX Session
while FIX session takes care of session & login connect/disconnect as long as
remote server allows. This would also mean that if session is not established,
FIX session will store all incoming messages from FIX application, and send
them once the remote connection has been restored?
Under what circumstances FIX Application itself may want to force login/logout
or session connect/disconnect....as it is not the function of Application Layer
itself.
--Many Thanks :)--
[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.
