[This message was posted by Jim Northey of The LaSalle Technology Group <[email protected]> to the "General Q/A" discussion forum at http://fixprotocol.org/discuss/22. You can reply to it on-line at http://fixprotocol.org/discuss/read/e734377e - PLEASE DO NOT REPLY BY MAIL.]
The approach we have come up with is to create configuration rules that define how to handle fields that overlap. For instance MsgType=D should be unknown to FIXT.1.1 But MsgType=D is known for FIXT.1.1+FIX.[45]* There are other fields. Phil and Ryan did separate analyses on this. We are close to having both: 1) Configuration rules for dynamically binding and 2) producing static, pre-configured repositories for use by member firms. [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.
