|
FAST Protocol
< Previous Next >
Re: OPRA is not FAST
Rolf Andersson / Pantor Engineering
31 Oct 2008 10:13AM ET It was mind over matter.
(They don't mind because we obviously don't matter to them)
> Jim, This has been a long standing issue with OPRA that seems to have
> fallen on deaf ears. It all started when OPRA simply used the proof on
> concept code that SpryWare and Pantor wrote to demonstrate the concept
> of FAST and released it as a production feed. They never consulted the
> group to review their implementation, in fact they distributed decoder
> source coded that still contained the original proof of concept cvs
> version control headers.
>
> The proof of concept code was not FAST compliant, because FAST was not
> even formalized at that point. I do believe they consulted Jordan and
> Jordan before releasing their version 2 of OPRA FAST, "OPRA FAST for
> Symbology", about correcting the non compliant portions of the code. For
> some reason they chose not to bother.
>
> So you are left with a feed that cannot be decoded with a generic FAST
> decoder. The changes are minor, simply adding a few more templates
> rather than having messages templates dynamically changed based on
> message content.
>
> /Daniel
>
>
> > OPRA is not a FAST compliant market data feed - it is FAST-like but is
> > not compliant with the FAST Specification. What are other vendors
> > doing to address the OPRA Market data feed - which should not be
> > confused with being a FAST market data feed? We are a bit concerned to
> > alter or break our standard implementations to support OPRA. Seems
> > like an alternative product or code branch might be preferred to
> > corrupting the main code line of a FAST compliant product.
OPRA is not FAST Jim Northey / The LaSalle Technology Group 31 Oct 2008 9:38AM ET Re: OPRA is not FAST
Rolf Andersson / Pantor Engineering 31 Oct 2008 10:13AM ET
|
@FIXProtocol
