|
From: Toli K. <to...@ma...> - 2006-09-29 01:58:20
|
Steve, I'm still working on this, but i got a work project that took priority. i'll come back to this next week and post a version. On 9/24/06, Steve Bate <st...@te...> wrote: > QuickFIX/J Documentation: http://www.quickfixj.org/documentation/ > QuickFIX/J Support: http://www.quickfixj.org/support/ > Hi Toli, > > I'm open to adding more configuration to the JdbcLogFactory. > If you'd like prototype the changes, that would be great. If > you had some related unit tests that would be > even better. ;-) In the longer term, I'd like to have a > general FIX message to relational table mapping capability > so that, for example, NewOrderSingle could be mapped to > an application-specific database structure with columns > for whichever fields are important to that specific > application. The database logger would be implemented as > a special case usage of this mapping framework. > > I'll be on the road on Monday, so I'll watch for other > comments when I return on Tuesday. > > Steve > > > -----Original Message----- > > From: qui...@li... > > [mailto:qui...@li...] On > > Behalf Of Toli Kuznets > > Sent: Saturday, September 23, 2006 2:49 AM > > To: qui...@li... > > Subject: [Quickfixj-users] RFE: Making LogFactories more confgurable > > > > QuickFIX/J Documentation: http://www.quickfixj.org/documentation/ > > QuickFIX/J Support: http://www.quickfixj.org/support/ 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. > > > > -------------------------------------------------------------- > > ----------- > > Take Surveys. Earn Cash. Influence the Future of IT Join > > SourceForge.net's Techsay panel and you'll get the chance to > > share your opinions on IT & business topics through brief > > surveys -- and earn cash > > http://www.techsay.com/default.php?page=join.php&p=sourceforge > &CID=DEVDEV > > _______________________________________________ > > Quickfixj-users mailing list > > Qui...@li... > > https://lists.sourceforge.net/lists/listinfo/quickfixj-users > > > > > ------------------------------------------------------------------------- > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to share your > opinions on IT & business topics through brief surveys -- and earn cash > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > _______________________________________________ > Quickfixj-users mailing list > Qui...@li... > https://lists.sourceforge.net/lists/listinfo/quickfixj-users > -- Toli Kuznets http://www.marketcetera.com: Open-Source Trading Platform download.run.trade. |