Re: [Quickfix-developers] Incoming Message Log

[Oren M. <ore...@ya...>]

Martin,

The log currently doesn't server this purpose.  The
logging in QuickFIX is rather primitive, and is
intended for plain old logging as opposed to data
storage.

If you do want to use the logs in this manner, you
would have to write something yourself.  This would be
easy to do as you can just use the Message class to
parse each line for you.  So you essentially need to
read a line, pass it into the message along with the
sessions data dictionary, and then you will have
everything.

This is a little risky to do with logs.  If you do
this you will have to make sure to clear the logs
everyday, otherwise messages get appended and you will
have stale orders from the previous day.  You may want
to consider just storing messages of interest coming
from the fromApp callback instead of relying on the
logs, who'se implementation may change in the future. 
For instance we have discussed combining the incoming
and outgoing logs into one file so the sequence of
message processing can be accurately viewed.

--oren

--- "Martin.Derkenne" <mar...@ac...>
wrote:
> Hi,
>  
> It would be very convenient for me to access the log
> file for the
> incoming message stream. This would allow me to
> build up a picture of
> the trades and orders present for a user during the
> trading day (where a
> client reconnects to a cut-down FIX 4.1 server)
>  
> It seems that there is currently no programmatic way
> to really access
> the contents of the incoming log file - it is
> hidden. I can fetch
> messages from the store, but not from the log. 
>  
> The question is to customize or not. Have I missed a
> path to request the
> QuickFIx library to fetch these log messages for me,
> or do I need to
> implement my own specialty class? I suspect the
> latter. 
>  
> Any comments appreciated
>  
> Martin Derkenne
> 

__________________________________
Do you Yahoo!?
Yahoo! Search - Find what you’re looking for faster
http://search.yahoo.com