|
PureBytes Links
Trading Reference Links
|
Mark,
your are opening the door widely for various Spammers. If you want to
beta-test your stuff make a beta-test version - I am still waiting
for one. Just keep vaporware off the list.
Gerrit Jacobsen
> From: "Mark Brown" <markbrown@xxxxxxxxxxxxx>
> To: <fritz@xxxxxxxx>, <omega-list@xxxxxxxxxx>
> Subject: Re: TraderWare Wish List
> Date: Thu, 29 Apr 1999 10:50:16 -0500
>
> > Here are a bunch of wish list items. I consider the first three CRITICAL,
> and the last two are wishes.
> >
> > * I want the ability to examine and edit the incoming tick stream. I
> don't know if this makes sense given the "Quote.com model" that I think TW
> is using, where the data feed constructs and sends out bar data.
>
> NO! this is not how we do it, we looked at the Quote.com data and thet are
> doing what they are because of resourse problems. We do not construct and
> send out bar data. we send every tick of everthing you specify and the bars
> are made up on your side from the historical database that is being created
> on your hard drive. only the latest tick data is comming from us not the
> entire bar history. so we are a sort of send and append feed.
>
> > But I would assume TW receives each tick even if I'm using N- minute bars.
> otherwise it couldn't trigger stops instantly.) I know TW supports
> correction of bad ticks, but I strongly suspect that TW's corrections may be
> too late for many uses. E.g. Quote.com corrects bad ticks, but it may take
> several minutes before that happens. That's way too late if the bad tick
> tripped your stop, or triggered a false high/low pattern. I want to be
> able to view EVERY tick as it is received, ***BEFORE*** it enters into the
> TW platform and impacts my systems, and optionally remove ticks that **I**
> decide are bad according to **MY** criteria. That may include comparing the
> tick to the current bid/ask, or looking at the tick in relationship to
> previous and even later ticks (i.e. suspect ticks could be held until the
> next tick comes in to see if it was anomalous), etc.
>
> I want to be able to view EVERY tick as it is received, ***BEFORE*** it
> enters into the TW platform and impacts my systems, and optionally remove
> ticks that **I** decide are bad according to **MY** criteria.
>
> BUDDY THAT'S EXACTLY THE WAY WE DO IT!!!!! we send you the data first and
> then your application does with the data whatever you want. we have a "real
> time" auto correction scrubber. you will have the option to use it or not
> to use it.
>
>
> > * I want ACCURATE representation of slippage. You should be able to
> specify the TIME it took between order execution and fill, or the
> > POINTS of slip, or the WORST TICK within a certain window, etc. A fixed
> "$X per RT" just does NOT cut it. This is a must for volatile
> > markets like the S&P.
>
> in the trade simulator we have decided to either allow money for slippage or
> time, i like the time feature its more realistic especially in a fast
> market. it will make some paper traders very unhappy but it will give them
> a good strong dose of reality..too.
>
> > * Program notification when the system changes position, sets stops, etc.
> TS drives me bananas because it just "beeps" at me when it buys
> > or sells. I want my CODE to be notified so I can do things like sound an
> un-missable alarm, send a pager message, set stops based on
> > the conditions at the time of entry, etc. If you're brave you could even
> use this to submit an electronic order. :-)
>
> no comments right now on these ; - )
>
> mb latter
>
>
|