[This message was posted by Russell Curry of Assimilate Technology, Inc. 
<[email protected]> to the "4.4 Changes" discussion forum at 
http://fixprotocol.org/discuss/17. You can reply to it on-line at 
http://fixprotocol.org/discuss/read/594e2cf8 - PLEASE DO NOT REPLY BY MAIL.]

Hi Charles,

I would have to agree with other posters here that QuickFIX/C++, for all 
intents and purposes seems to be pretty stagnant. The same cannot be said for 
QuickFIX/J, which appears to have both a very active user community and 
development team.

Are you looking for an OSS solution for a specific language? If you are doing 
anything with .NET/C#, you might consider taking a look at the open-source FIX 
engine my company has released - it's called VersaFix and can be found at:

http://www.sourceforge.net/project/versafix

We also have a local resource page for the project at our corporate site, which 
is at:

http://www.assimilate.com/Products/VersaFix

If you are not targeting .NET, I would highly recommend that you consider 
QuickFIX/J instead of QuickFIX/C++. The reason for this is that the folks that 
are running the QF/J project are putting work into ensuring that it stays 
current with the FIX protocol, while the QF/C++ project doesn't provide out of 
the box support for versions of FIX that are later than 4.4. If you just need a 
point solution for a version of FIX before FIX 5.0, you are still quite safe 
with QF/C++.

Cheers.


> Hello,
> 
> I was wondering if anyone knows anything about the QuickFix project
> and if there are any later development work done on this open
> source library.


[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.

Reply via email to