[This message was posted by Russell Curry of Assimilate Technology, Inc. <[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/b859fb24 - PLEASE DO NOT REPLY BY MAIL.]
> Hi, > > I am a relative newbie to the FIX world and was looking to design a > faily reusable configuration format for setting up FIX sessions and > custom plugins. > > The idea here is to be able to take the configuration and be able to use > it to customise a different FIX engine (custom build or off the shelf) > with minimal changes. > > I would appreciate any ideas/articles/thoughts on this subject. > > Thanks in advance for your help! > > ~Arpita Hi Arpita, Since you're asking for ideas, here are my thoughts - if you are going to try and build a universal configuration system of some sorts, you should start out by just taking a look at the configuration systems that are used by various FIX engines. If you don't have access to any of the commercial ones, start with the open source ones like QuickFIX, QuickFIX/J, or VersaFix - you can google any of those terms for more information, and just take it from there. By looking at the configuration schemes from a couple of different engines, you should be able to get a reasonable idea of the common criteria that are used across engines to configure them. Cheers, Russ [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.
