{{Quickfixn}} Best way to handle custom messages

Grant Birchmeier gbirchmeier at connamara.com
Wed Mar 26 15:14:05 PDT 2014


For best results, I recommend regenerating the QF source and rebuilding QF.
 The v1.5.0 tag is the latest release.

It does require Ruby, though.  That does bother some people.


On Wed, Mar 26, 2014 at 4:39 PM, Francis Gingras <
francis at tradeintegration.com> wrote:

>  I have a counterparty that sends custom messages (e.g. UAF, UBB) with
> FIX4.2 headers. They also send RequestForPosition (UAN) in the FIX4.2
> session. What is the best way to handle this? I'd like to avoid having to
> maintain a custom build of QF/n.
>
> 1) Do I create custom message classes and inherit QuickFix.FIX42.Message?
> (I doubt Crack() will handle these so I would have to use a non type-safe
> crack method).
> 2) Any other way?
>
> Thanks,
>
> Francis
>
> _______________________________________________
> Quickfixn mailing list
> Quickfixn at lists.quickfixn.com
> http://lists.quickfixn.com/listinfo.cgi/quickfixn-quickfixn.com
>
>


-- 
Grant Birchmeier
*Connamara Systems, LLC*
*Made-To-Measure Trading Solutions.*
Exactly what you need. No more. No less.
http://connamara.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.quickfixn.com/pipermail/quickfixn-quickfixn.com/attachments/20140326/f99d06d6/attachment-0002.htm>


More information about the Quickfixn mailing list