[This message was posted by Russell Curry of Assimilate Technology, Inc. <r...@assimilate.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/91bfdbff - PLEASE DO NOT REPLY BY MAIL.]
> Hi, > > I'm fairly new to FIX, having come from a SWIFT-type background. > > The most significant difference appears to be transport of the messages. > Is there anyone who could describe how I would know in the TCP stream > when it was ok to send a message? Hi Dave, I'd suggest that you take a look at the source code for one of the open source FIX engines, if you'd like to see some different approaches to managing FIX message traffic over TCP sockets. Here are links to the major ones: 1. QuickFix (C++ & Managed Wrappers) http://www.quickfixengine.org 2. QuickFix/J (Java Implementation): http://www.quickfixj.org 3. VersaFix (.NET/C# Implementation): http://www.sourceforge.net/projects/versafix The complete source code for all of these different engines is available from their respective websites, and they serve as good examples of how to build your own FIX message processing code. Cheers, Russ [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-proto...@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.
