Imported from previous forum
[ original email was from Charles Easton - upchuk@optonline.net ]
FIX4NET is a open source .NET FIX engine. The previous version supported FIX 4.0 and 4.2. A number of people have shown interest in using the software so I have taken it to the next step…
The latest FIX4NET 0.5.0.0 has been released and supports FIX 4.4.
FIX4NET is a open source .NET FIX engine. The previous version supported
FIX 4.0 and 4.2. A number of people have shown interest in using the
software so I have taken it to the next step…The latest FIX4NET 0.5.0.0 has been released and supports FIX 4.4.
Hi Charles,
actually I wonder about the difference to QuickFIX (http://www.quickfixengine.org) which also supports .NET via C#.
Please, provide some details.
Thanks, Jörg
[ original email was from Charles Easton - upchuk@optonline.net ]
> > FIX4NET is a open source .NET FIX engine. The previous version
supported FIX 4.0 and 4.2. A number of people have shown interest in
using the software so I have taken it to the next step…The latest FIX4NET 0.5.0.0 has been released and supports FIX 4.4.
Hi Charles,
actually I wonder about the difference to QuickFIX
(http://www.quickfixengine.org) which also supports .NET via C#.Please, provide some details.
Thanks, Jörg
First let me say QuickFIX is a great product with support for FIX 4.0, 4.2, and 4.4. It’s versatile and fast.
-QuickFIX uses .NET wrapper to make un-managed C++ api calls while FIX4NET is 100% .NET.
-FIX4NET supports 64-bit or 32-bit hardware. Since QuickFIX uses un-managed C++ calls it only support 32-bit.
-FIX4NET support faster message rates.
-FIX4NET has a easier OO model. Creating messages and populating values is simpiler.
-FIX4NET supports offline send. If enabled you can Send messages while disconnected. The messages gets stored and will be transmitted when the connection is established.
I am sure there is more…
First off, congratulations on getting this out there. Having a pure .NET implementation available is a great thing. Above all you will have the ability to make your product more .NETtty which is no small advantage. Just a couple of clarification though.
-QuickFIX uses .NET wrapper to make un-managed C++ api calls while
FIX4NET is 100% .NET. -FIX4NET supports 64-bit or 32-bit hardware. Since
QuickFIX uses un-managed C++ calls it only support 32-bit. -FIX4NET
If built with a 64 bit compiler, QuickFIX does support 64 bit hardware.
-FIX4NET supports offline
send. If enabled you can Send messages while disconnected. The messages
gets stored and will be transmitted when the connection is established.
QuickFIX also supports this.
I can’t speak to the others but there isn’t a real need to justify differences apart from the ground up .NET appeal. This was the original and primary differentiator between QuickFIX and QuickFIX/J for java developers, and I’m sure there is a similar desire for .NET developers.
FIX4NET is a open source .NET FIX engine. The previous version supported FIX 4.0 and 4.2. A number of people have shown interest in using the software so I have taken it to the next step…
The latest FIX4NET 0.5.0.0 has been released and supports FIX 4.4.
Can you please send me the direct link to download the latest code to support latest FIX version 5.0?