I started working on this last year, and frankly found the task to be beyond me. Given the constraints imposed by my employer, I ended up writing only what I needed in C++.
My regrets. If you could sketch what you need (besides the low-level "Add a field" and "Determine the message check-sum") I'd be happy to give it another try.
- Does one include tag-validation? (My employer required custom-tags for his messages.)
- Does the user provide his own transport-mechanism, or do you need the FIX library to send and recieve messages?
- Support for all versions?
In the meantime, unless you're writing both sides of the FIX connection, whoever you're worjking with should have a QA environment you can test with. (NASDAQ, for example, helps you test a new FIX connection.)
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
| |
For: |
|
Use: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.