[This message was posted by Rolf Andersson of Pantor Engineering 
<[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/36da030b - PLEASE DO NOT REPLY BY MAIL.]

Sat,

as Dale points out, the pmap bit should be set in the third message.
the example in your latest mail is incorrect

/Rolf

> > > I have issue with encoding template Id with multiple templates. If
> > > the the input encoding template Id is of type COPY_CODE and the
> > > order of encoding is t1, t2 and t1; how the decoder will understand
> > > the template Id for t1 second time. Since it comes with PMAP bit set
> > > to 0 and decoder dont have any idea of previous one( which could
> > > take to
> > > t2). Can anybody throw light on this ?
> >
> > The PMAP bit for the template ID will be one in the second and third
> > messages in your example. It will probably be a one in the first
> > message, too, depending on what happened before this message was sent.
> >
> > If not there is an error in the encoder.
> >
> > Dale
> 
> Thanks for your reply, here template Id is not common across the
> messages. Each message is having different template Id. For the
> corresponding message, if it is already present in the previous message,
> so it wont send again.(since its COPY CODE ).
> 
> Message 1 : templaet Id = 1, bitmap =1 Message 2 : template Id = 2 ,
> bitmpa = 1 Messaeg 3 : template Id = 1 , bitmap =0 ( since its already
> encoded for that template previously)


[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