[This message was posted by Niketan Mhatre of Marketplace Technologies <[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/5d54db59 - PLEASE DO NOT REPLY BY MAIL.]
> > It is definitely possible to implement a FIX engine in C#, it can be > done in any language that supports TCP sockets. > > It will be very hard for anyone to give you a clear answer as to the > performance impact of using C# instead of C++. A well written C# engine > will outperform a C++ engine that was not written and tuned quite as > well. Unless your team is all C++ experts, performance is absolutely > critical, you have clearly defined (and written) performance goals and > your development schedule has the extra time C++ will require, I’d > advise using C#. > > That said, why are you building a FIX engine from scratch? Why not using > QuickFIX with the .NET bindings? Thanks for quick reply. Performance is quite critical but i guess my clients won't be capable of testing engine to its optimum capacity. I meant developing from scratch means i will abolish my ad hoc protocol totally else it was possible for me to embed FIX instead of ad hoc protocol :). Currently i had been presented with some exchange document supporting FIX protocol (as well as non FIX which is developed at our end). BTW i got the quickfix website , Let me go around it. I am more like to develop FIX engine in C# and then tune performance as per client's demands. Thanks :) [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 -~----------~----~----~----~------~----~------~--~---
