|
PureBytes Links
Trading Reference Links
|
"Within the next few weeks we will be revealing a complete detailed plan to
our clients explaining the changes to the data feed."
When DBC took over BMI, they downgraded BMI clients to 38.4 from BMI's real
fast 56K V-Line. I think all DBC would have to do is reupgrade everybody to
this faster service (if they didn't sell it off). I remember getting a lame
story about how the new 38.4 was just as powerful as the 56K. This didn't
make any sense since opted to go with the 56K V-Line for some reason, having
the 38.4 speed available too. DBC said thier compression method made it
eqivilent. Yeah, right. How does adding a layer make it faster or better?
> -----Original Message-----
> From: rickinri@xxxxxxx [mailto:rickinri@xxxxxxx]
> Sent: Saturday, January 15, 2000 9:14 AM
> To: code-list@xxxxxxxxxxxxx; omega-list@xxxxxxxxxx; Thomas Brun;
> tradejacker@xxxxxxxxxxxx; Jay Becker; teits@xxxxxxxxx; teits@xxxxxxxxx;
> Dave; Jay Becker; teits@xxxxxxxxx; teits@xxxxxxxxx
> Subject: CL_(Fwd) RE: (Fwd) Re: Fw: BMI Satellite
>
>
>
> ------- Forwarded Message Follows -------
> Date sent: Sat, 15 Jan 2000 09:10:57 -0800
> From: TSBMI <tsbmi@xxxxxxx>
> Subject: RE: (Fwd) Re: Fw: BMI Satellite
> To: "'rickinri@xxxxxxx'" <rickinri@xxxxxxx>
> Copies to: TSBMI <tsbmi@xxxxxxx>
>
> Dear Client,
>
> Thank you for your Email. You state that client in the lower 48 states are
> seeing different times and tick counts many factors will cause this
> difference the baud rate your unit is at, reception, your software can all
> play factors in this. As for the 2 minute delay you are seeing I am in the
> process of looking into it I tend to think that this maybe an
> issue stemming
> from the volatility of the stock market that has had an effect in our data
> stream since the first of the year. BMI is on a fixed bandwidth
> meaning that
> regardless of what the situations we only have so much room to fit all of
> the data into this bandwidth this may cause back up of data and buffering.
> We are currently working on a permanent solution to this issue. Within the
> next few weeks we will be revealing a complete detailed plan to
> our clients
> explaining the changes to the data feed.
>
> Thank You,
>
>
> Daniel A. Pursley
> DBC TECH SUPPORT
> 1.800.436.4036 BMI/1.800.762.7538 DBC Products
> > Please visit our website at http://www.dbc.com
> >
> >
> > -----Original Message-----
> > From: rickinri@xxxxxxx [SMTP:rickinri@xxxxxxx]
> > Sent: Wednesday, January 12, 2000 10:45 PM
> > To: tsbmi@xxxxxxx; tdbrun@xxxxxxxxxxxxxxxx
> > Subject: (Fwd) Re: Fw: BMI Satellite
> >
> > Daniel A. Pursley
> > DBC TECH SUPPORT
> > ------- Forwarded Message Follows -------
> > Date sent: Wed, 12 Jan 2000 11:36:42 -0600 (CST)
> > From: tradejacker@xxxxxxxxxxxx
> > To: Roger Dalton <rogerdalton@xxxxxxxxx>
> > Copies to: omega-list@xxxxxxxxxx
> > Subject: Re: Fw: BMI Satellite
> >
> > i'm in texas, and yep, i've got the 38k box.
> >
> > what i find amazing is that bmi sat subscribers are reporting different
> > ticks counts and different time delays across the lower 48 us.
> >
> > agreed that your 2 min delay is not only a disaster, but
> ILLEGAL in terms
> > of reat time delivery in our contracts.
> >
> > maybe we should sue bmi to give us the 56k delivery that they promised
> > before
> > bmi was swallowed up by dbc!!!
> >
> > TJ
> >
> > i'm posting this private message because of the general concern
> over bmi
> > shoddy and inconsistent delivery service....we paid for a
> premium service,
> > and damnit to hell, we should get what we pay for
> >
> > jeff crystal, as a bmi/dbc rep, where the hell are ya??????
> >
> > At Wed, 12 Jan 2000 08:27:24 -0800 (PST), Roger Dalton
> > <rogerdalton@xxxxxxxxx>
> > wrote:
> >
> > >
> > >I don't mind 5 second delays, but 2 minutes is
> > >disaster. I also just watch CME futures (S&P, Nas,
> > >Eminis) and a few indexes. That's it. I was making
> > >market orders in the eminis and just getting killed
> > >with my fills. Then I found out how delayed I was.
> > >
> > >You have a 38k satellite receiver box?
> > >
> > >Where are you located?
> >
>
|