[This message was posted by Dean Kauffman of TradeWeb LLC <dean.kauff...@tradeweb.com> 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/a2b4f0bc - PLEASE DO NOT REPLY BY MAIL.]
I use C++ QuickFIX to build simulators and sample applications, but a number of our customers have built to our API using QuickFIX/J. Both are equally reliable but only QuickFIX/J has been upgraded to 5.0. On the other hand the C++ version can be significantly faster. QuickFIX is not a standalone FIX engine but an object library. The typical way of implementing is to build your application around the libraries and deploy a single executable (C++) or a .jar file (Java). This means that it's easier to build a Java application around QuickFIX/J and a C++ app around QuickFIX. > Hi, Thanks for the quick reply. I'm at a new firm (formely of BofA) and > we're essentially a .NET shop here, although we are installed webMethods > as an ESB which is Java based. > > I've heard that QuickFix is no longer being supported and all the > resources are going into QuickFix/J. Is this true? Once I have the > engine up and running does it matter what language I am developing in? > I'm assuming that the FIX engine is a stand-alone entity that we > communicate with ....no? > > Thanks for any more info. [You can unsubscribe from this discussion group by sending a message to mailto:unsubscribe+100932...@fixprotocol.org] --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Financial Information eXchange" group. To post to this group, send email to FIX-Protocol@googlegroups.com To unsubscribe from this group, send email to fix-protocol+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/FIX-Protocol?hl=en -~----------~----~----~----~------~----~------~--~---
