[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/acba8e18 - PLEASE DO NOT REPLY BY MAIL.]
Hi Russ, I do not think a message in a discussion forum would give any good picture of adoption of FIXT + FIX in the real world. Instead FPL office could send out a survey / questionnaire to all member firms http://fixprotocol.org/members/ and all companies listed as FIX Products and Vendors http://fixprotocol.org/products/all and compile the results of such a survey. Questions in the survey could be like Q1. Which versions of FIX do you support (select all that apply) {list all versions here} Q2. What asset classes do you deal with (select all that apply) {list all asset classes here} Q3. Does your firm support any Non-FIX protocols Q4. Does your firm use FIX internally for communication between systems Q5. Does your firm use FIXML internally for communication between systems Q6. Does your firm plan an upgrade of FIX version ? Yes / no Q7. If you answered yes to Q6 which version(s) are you planning to support(select all that apply) {list all versions here} Q8. Does your firm's FIX systems use Message Types from higher versions ? Yes / no Q9. Does your firm's FIX systems use Tags from higher versions ? Yes / no Q10. Does your firm's FIX systems use Custom Message Types ? Yes / no Q11. Does your firm's FIX systems use Custom Tags ? Yes / no We could discuss in this Thread what additional questions could be asked. Response to such a survey could be classified by organization type and that would provide an insight into usage of FIXT + FIX In my previous project, I was given the task of analyzing upgrade of the FIX.4.0 US Equities and options only Broker Trading application (takes NewOrderSingle from clients and routes them to exchanges & forwards ExecutionReports received from Exchanges to clients) upgraded to FIX.4.2+ to add support for complex options using NewOrderMultileg, FixedIncome etc. I suggested FIXT.1.1 and the management's view was FIXT.1.1 is too complex which does not add any benefit to the business. Regards, K. Mahesh > Hi All, > > I've been wondering how many people are actually using all of the > features of FIXT+FIX in the real world? Although I like the separation > of the session layer from the application layer, in the context of > transporting non-FIX messages, and even regular FIX messages if the > layer separation was really being taken to heart, I wonder how much of > this just makes things more complicated from the perspective of people > who are already managing existing FIX engines/systems? > > I know that even from the greenfield project perspective, for example > the VersaFix OSS engine we've been developing, actually implementing the > FIXT+FIX stuff can be pretty complicated, so I wonder how many people > are actually retrofitting all of this into their existing products - is > this really being well received across all the firms that have existing > engines and products that are used to dealing with FIX messages from the > 4.2-4.4 perspective? [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.
