[This message was posted by Mahesh Kumaraguru of <[email protected]> to the "4.4 Changes" discussion forum at http://fixprotocol.org/discuss/17. You can reply to it on-line at http://fixprotocol.org/discuss/read/469faa95 - PLEASE DO NOT REPLY BY MAIL.]
Jay, Could you point me to the FIX documentation which stated "header and body tags should not be intermixed." I have written a FIX broker simulator in Java which tests three different Buy side systems (two of them in FIX.4.2 and one in FIX.4.0) and none of them reject messages with intermixed header and body tags as incorrect. John, Since FIX.4.0 "The general format of a FIX message is a standard header followed by the message body fields and terminated with a standard trailer. Each message is constructed of a stream of <tag>=<value> fields. Except where noted, fields within a message can be defined in any sequence (i.e. relative position of a field within a record is inconsequential); exceptions are explicitly defined otherwise (certain header fields and fields within repeating data groups)." So FIX.4.4 introduced no new Field ordering requirements compared to FIX.4.0. Upto FIX.4.4 for 8, 9 and 35, there is explicit mention as first, second and third fields of "every" FIX message, but there is no such mention for any other fields. Regards, K. Mahesh [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 -~----------~----~----~----~------~----~------~--~---
