|
From: Toli K. <to...@ma...> - 2006-09-23 00:49:24
|
Hey everyone, We are thinking of using the JdbcLogFactory to save some of the FIX messages to the database. (side question: anybody ever tested throughput/efficiency of that logger?) However, compared to the ScreenLogFactory, the Jdbc and Mysql loggers are very bare-bones and not configurable. for example, the target table names where the messages are placed are hard-coded (see the rfe at http://www.quickfixj.org/jira/browse/QFJ-75 Does anybody have any thoughts on improving the other loggers? Currently, there are 4 vars for configuring ScreenLogFactory that turn on/off some printing. We'd like to have similar ones for the JDBC logger as well - which would mean 4 more similar variables. I'd be happy to prototype the new changes, and submit a patch for review. Any thoughts/considerations before i do that? In production, we'll most likely use a CompositeLogFactory, which will output to the screen and/or DB depending on which configs are specified. However, we may want to have different output going to each, hence the need for parallel config parameters. looking forward to hearing suggestions -- Toli Kuznets http://www.marketcetera.com: Open-Source Trading Platform download.run.trade. |