[This message was posted by Daniel May of SpryWare, LLC <[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/a63e5461 -
PLEASE DO NOT REPLY BY MAIL.]
David,
Are you talking about FASTOR ? Or OPRA ? Opra uses the scheme where
the second half of the message is defined by a field in the message itself, but
FASTOR does not do this. Each FASTOR message has one of 4 possible template
ID's, 'T', 'Q', 'B', 'A'. The FAST template for each of these messages is
unique. The encoding scope however for some of the fields may be either global
or local to the tid. When implementing this using the fastapi 1.0, it was a
bit misleading if you try to read the definition from the source code. To
implement global and local encoding, the code reads as if you need to branch on
fields within a messages to decode later fields. That is not the case, it is
only needed to support the scope of the encoding. As far as I know, the FASTOR
template definitions are 1.1 compliant.
I do believe at one point Jacob Northy put together a set of FAST 1.1 xml
templates to define the FASTOR schema, and was able to decode the data with his
"off the shelf" decoder. Let me see if I can find those.
/Daniel
> Hi David --
>
> Thanks for great idea! In this case the message identifier is in fact
> the first field, so your trick should work nicely.
>
> But in general, this seemed like a nice thing you could do with 1.0
> (albeit only through coding); it's too bad it didn't make it somehow
> into the template definitions for 1.1.
>
> Perhaps while we are talking about enhancements to the standard, we
> might consider some sort of ability to map a field to a template
> identifer?
>
> > Hi David,
> >
> > No, the only "field" that has this power is the template identifier.
> > Once you're decoding a given template, the number of logical fields
> > cannot change.
> >
> > Is the field that indicates the structure the first field of the
> > message?
> >
> > If so, it could be possible to pretend it actually is the TID and have
> > the real value of that field constant coded in the corresponding
> > template. But I've too little information to say if it would fly in
> > your particular case.
> >
> > /David
> >
> >
> > > The question is really this:
> > >
> > > Is there a way of using FAST 1.1 templates to describe an encoding
> > > scheme where the template for the second half of the message is
> > > determined by the value of a field in the first part of the message?
> > >
[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
-~----------~----~----~----~------~----~------~--~---
