[This message was posted by Jim Northey of The LaSalle Technology Group <[email protected]> to the "FIXimate Enhancements" discussion forum at http://fixprotocol.org/discuss/53. You can reply to it on-line at http://fixprotocol.org/discuss/read/de291365 - PLEASE DO NOT REPLY BY MAIL.]
Mahesh, Look for the CME system identifier and the NGM logon proposal. In addition to requiring ApplVerID on each message to simplify maintenance of state. > Jim, > > Can I have any documents related to FIXT.1.2 changes. > > Regards, > K. Mahesh > > > Eventually you are correct. Right now as we only have one session layer for > > FIX.5.0 through FIX.5.0SP2 - we have left the repository consolidated. If > > the only think today that can be used is FIXT.1.1+FIX.5.0, > > FIXT.1.1+FIX.5.0SP1, etc. Why separate the repository right now. However, > > FIXT.1.1 can be used to communicate other payload besides FIX so it needs > > to be represented stand alone. > > > > It looks like FIXT.1.2 will be released in the near future and then we have > > to resume the work we started on configuring a session layer plus a n > > application layer. > > > > > [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.
