|
PureBytes Links
Trading Reference Links
|
"To interested parties"
as my sojourn continues into the foray of platform/data providers, i thought
those interested might benefit form the following extraordinarily PROMPT and
couteous reply(ies) from my ongoing correspondence with Howard Arrington of
Ensign: Lee
<The primary differences between the BMI feed and the DBC On-Line Internet
feed are these:
BMI: EW will automatically build quote tables with all symbols on the feed,
ie. 100,000+
DBC: User is restricted to 500 symbols and must enter which ones in a watch
list.
BMI: EW maintains all data on all symbols and uses data to build intra-day
charts.
DBC: Basically the same, but also have DBC tick server that will replace
missed data up to 2 days back. This is a valuable and need feature because
of the disconnects associated with using the Internet. When you reconnect,
the missed intra-day data is requested and charts heal themselves.
BMI: EW can connect directly to the serial port, or use the DBC Data
Manager with the BMI receiver box.
DBC: EW must use the DBC Data Manager as it does the Internet connection
and reception.
If you use the Data Manager, it is basically a server and more than one
application can run simultaneously and receive data from the data manager.
Your secondary server to the bid/ask information would probably be best
implemented by connecting to the Data manager and receive the same records
from DM as EW receives. Each record is an easy to use record with all
defined fields already filled in. You would reference the data is
something like rc.bid or rc.asksize.
Speedwise, it seems like the Internet is typically a couple seconds ahead of
the receiver box, amazing as that might seem. Most user feedback complains
that the Internet solution is not as reliable as when they used a receiver
box.
Sincerely,
Howard Arrington>
http://www.ensignsoftware.com/
|