[This message was posted by Rufus Me of Self <[email protected]> to the "FAST 
Protocol" discussion forum at http://fixprotocol.org/discuss/46. You can reply 
to it on-line at http://fixprotocol.org/discuss/read/198bef35 - PLEASE DO NOT 
REPLY BY MAIL.]

What troubles me about this coming CME change is that they are drifting away 
the FAST standard.  The prepending of sequence number and a "sub-channel" ID, 
outside the actual FAST message itself, just seems kludge to me.

Of cos, I could understand pragmatically why they are doing it, it allows some 
"pre-processing" of the message block without incurring the "initialization 
cost" of FAST decoder.  But a well constructed FAST decoder with JIT decoding 
mechanism can do the job just as it.  I look the FAST processor is essentially 
a bit-shifter (for lack of a better phrase).  And with processing speed at 
5/6/7M+ msgs / sec, I don't see the need to deviate from the FAST standard.

I will fire off an e-mail to CME (as an equity member), and see what the 
thinking behind the scene is.

> I looked at the document - this is just a case of confusing
> documentation and a bit of unfortunate document titling.
> 
> This is "CME FIX/FAST 2.0" which I believe is based upon FIX/FAST 1.1
> features (the documentation doesn't say) would be nice if someone from
> CME could post a clarification.
> 
> It would be nice to know which versions of FIX/FAST were used to create
> CME's CME FIX/FAST 1.6 and CME FIX/FAST 2.0.
> 
> For the record there is no FIX/FAST 2.0 in the plans as Rolf and other's
> stated. There isn't even a FIX/FAST 1.6 which is a good indicator
> something was amiss.
> 
> And Rolf correct me if I am wrong - we don't have any enhancements being
> worked on at this time within the working group.
> 
> The Market Data Optimization Working Group that oversees FAST is open
> for participation by any FIX member. We encourage you to participate and
> contribute.
> 
> The FIX/FAST specification is open to anyone to use of course,
> regardless if you are a member of FIX or not.
> 
> > The CME's pdf is located here:
> > http://www.cmegroup.com/globex/files/FF20ClImp.pdf
> >
> > Title: FIX/FAST 2.0 Launch New Release Availability: 1 February 2010
> > Launch Date: 25 April 2010
> >
> > They claim in the pdf, that FIX/FAST 2.0 will be replacing the current
> > FIX/FAST 1.6. That should give people a hint that they are using their
> > own internal version scheme as what they are calling FIX/FAST 1.6 I
> > implemented using the FIX/FAST 1.1 specification found on this site. I
> > could be wrong about this, but this pdf has the first occurrence of
> > FIX/FAST 1.6 that I've ever seen.
> >
> >
> > > just got a mail a forum reader indicating that the next release of
> > > the CME FAST feed has been dubbed "FIX/FAST 2". I haven't checked,
> > > but I would guess you can get information about this release from
> > > the CME web-site.
> > >
> > > /Rolf
> > >
> > > > Hi Robert,
> > > >
> > > > afaik, FPL/mdowg doesn't plan to release a FIX/FAST 2.0 spec in
> > > > April. Where have you heard this? Could it be that some exchange
> > > > or other producer of a FAST feed is planning a release?
> > > >
> > > > /Rolf
> > > >
> > > > > Where can I get info about a FIX/Fast 2.0 spec?
> > > > >
> > > > > Thanks,


[You can unsubscribe from this discussion group by sending a message to 
mailto:[email protected]]

-- 
You received this message because you are subscribed to the Google Groups 
"Financial Information eXchange" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/fix-protocol?hl=en.

Reply via email to