[This message was posted by Mahesh Kumaraguru of <[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/abfb13e6 - PLEASE DO NOT REPLY BY MAIL.]
Are you planning to develop FIX Session initiator (client) or FIX Session acceptor (server)? If your goal of developing a FIX Engine is learning, then I would suggest you develop both - client and server, that way you would see both sides of the coin. You can use TCP Sockets for FIX connectivity. > Thanks Mahesh, > > For the first iteration, I'll use Java and a networking framework other > than MINA (just to force my self to do something different from QFJ). > Frankly this is as much an exercise in learning FIX as it is in software > engineering. > > > > Check the release notes / appendix of the specs to see differences > > between versions. In FIX repository, there is a "TOOLS AND SAMPLES" > > described as "Compare FIX Messages between versions (Sample > > Application.zip, 14KB) A simple XSLT that compares the Tags that make > > up each message in FIX to the Tags that make up the same message in > > another version. The results are displayed as a basic HTML document". > > This XSLT tool is available at > > > > http://fixprotocol.org/documents/874/Sample%20Application.zip > > > > (You need to be logged in to access the above zip. ) > > > > There are substantial differences in Session between FIX.4.0 / 4.1 / > > 4.2 after which the next change in Session is at FIXT.1.1. FIX.5.0 > > onwards use FIXT.1.1 > > > > FAST is a multicast session protocol for market data. Work is underway > > to compress any XML / FIXML data over a FAST Session but FAST is not > > being used for Order / Execution workflows. > > > > You are right that implementating a FIX engine from scratch will teach > > you a lot about the "wire level protocol". Best of luck in your > > learning. What technology do you want to use for coding ? > > > > > Hi, I'm fairly new to FIX. I've used APIs which hide much of the > > > protocol, but haven't done much with the wire level protocol itself. > > > > > > Mainly as a learning exercise, I'd like to implement a simple FIX > > > engine (although I know QuickFix/J is available as a free and > > > production level engine). > > > > > > I've printed out the 4.2 spec, but am overwhelmed at the idea of > > > going through all the version. > > > > > > Are there any documents which simply list the differences between > > > the versions? > > > > > > Am I basically correct in assuming that the session level protocol > > > is the same for all versions and that the changes are limited to > > > application level messages? > > > > > > I'm a little confused about the relationship between version 5 and > > > the FAST protocol. Does 5 use FAST or is FAST simply a session level > > > protocol and all versions (the application level parts) can be made > > > to sit on top of FAST? > > > > > > 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 -~----------~----~----~----~------~----~------~--~---
