search

larytet / larytet-master

Automatically exported from code.google.com/p/larytet-master
0 stars 1 forks source link

TradingDataLogger #5

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
Class TradingDataLogger probably should be moved to FMRShell.cs. Do we need
the class at all ? May be just three classes 
 _maofDataLogger
 _rezefDataLogger
 _madadDataLogger

will  do ?
All three can share the same parent K3DataLogger which is an AsyncLogger.

Original issue reported on code.google.com by larytet@gmail.com on 11 Oct 2009 at 11:47

GoogleCodeExporter commented 9 years ago 
CC to jquant

Original comment by larytet@gmail.com on 11 Oct 2009 at 11:47

GoogleCodeExporter commented 9 years ago 
I don't think we need TradingDataLogger - it's awkward. We create K300 instance 
for
each logger anyway, so no reason to have redundant unused resources within this 
class.

Another approach is to continue using TradingDataLogger, which will record three
different streams using a single shared K300 instance. I think that machine's
resources allow to have two additional COM objects (K300), no gain here.

Original comment by jerusale...@gmail.com on 11 Oct 2009 at 12:05