[This message was posted by Changpeng Yu of FT Computer Solutions <[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/dc68407a - PLEASE DO NOT REPLY BY MAIL.]
> Hi All, > > Recently I encountered some query about TAG 122 which is a header > message and will be included during resend messages session. I noticed > that this TAG might not be in sequence like from the beginning of the > message, starting after the SenderCompID/TargetCompID etc. The TAG seem > to appear in the middle of the body message or at the end of the > messages. Is there any way we can recognise which is a header TAG or > body TAGs etc? Do we have any FIX protocol info that will indicate which > TAG should come first or before? Thanks in advance! BeginString(8) and Bodylength(9) have to come first in sequence. Because some implementation may read them in first without verify other message contents. With whole FIX message read in buffer, any tag message can be found by a string scanning. For a faster approach, the whole FixMessage can be read in by two socket read. FixExpress finds message header first, the read in who Fix message. FixExpress is at http://www.eptop.com/FIX/FixExpress.htm. Good luck, peng [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 -~----------~----~----~----~------~----~------~--~---
