Re: [Quickfix-developers] How to suppress 35=X messages in log file

[Mike G. <mg...@co...>]

On Thu, May 30, 2013 at 2:52 AM, Gunnar Harms <gh...@hi...> wrote:

> Deriving from the FileLogFactory and from FileLog to create my own derived
> FileLog is probably easy but in the onOutgoing method of the Log object the
> message type is not available
>

I've run into this before myself and I agree that it might be nice to have
access to something other than the raw string in the Log interface.
 However, it is also desirable to log the message immediately (and
therefore raw) so that we have a record of it in case an error occurs when
we try to process it.  Maybe the answer is to augment the Log interface to
have onIncoming/onOutgoing and additionally onIncomingRaw/onOutgoingRaw
callbacks.  Then you could implement whatever makes sense for your app.

In the meantime, however: see Message::identifyType() in Message.h, which
takes a raw string and returns the MsgType.

-- 
Mike Gatny
Connamara Systems, LLC