|
PureBytes Links
Trading Reference Links
|
I think the whole issue of using the system clock for datafeed time stamps
is pure bs. And I damn well hope that the beta guys tell em that too!
Example of a common occurence: BMI datafeed stops or pauses at 3:13PM CST
on the DATAFEED and SYSTEM times. A few minutes later, the BMI datafeed
continues to deliver the ticks with the 3:13, 3:14, and 3:15PM CST DATAFEED
time stamps, but the SYSTEM clock now shows them at 3:16, 3:17, and 3:18PM
CST!!!!
The TS4 server continues to receive and process the ticks with the correct
DATAFEED time stamps as delivered from BMI at 3:13-3:15PM CST.
But what will happen with the TS2000i "server" and the situation described
above? Will the ticks even be collected and processed? Will your tick data
file end at 3:13PM CST for that day? I see a potentially huge problem with
tick database corruption. Also, consider what might happen if you paste in
some ASCII tick data from a guy who has incorrect time stamps relative to
your tick database time stamps. So much for the sharing tick data among
traders if it means corrupting your database.
These concerns are genuine since they might affect the stability of the
trading platform.
Tony Haas
Alan Courchene wrote:
>>While its probably better to wait for the release rather than trying to
speculate, I was thinking about the computer time stamp problem TS2000i.
If this is actually true, how would you best deal with the problem.(other
than not upgrading to 2000i)<<
|