Imported from previous forum
What are the reasons for separating the template declaration and template definition in Template Exchange?
The main benefit I can see offhand of having a separate template declaration is the ability to register a well-known template (i.e. one that is loaded by both parties prior to establishing a FAST Session). Another benefit is the ability to register one template definition with multiple template ids. This would allow routing messages based on template id.
In that case, why is the template id duplicated in the template definition message?
You’ve listed a couple examples of when a separate declaration is useful, and ther are other examples too, like when you want to dynamically rearrange the TID assignments due to volume statistics.
The reson a definition can also be a declaration is that this will be the most common case, that you define and declare at the same time, so this is for convenience and optimization reasons.
/David
What are the reasons for separating the template declaration and
template definition in Template Exchange?The main benefit I can see offhand of having a separate template
declaration is the ability to register a well-known template (i.e. one
that is loaded by both parties prior to establishing a FAST Session).
Another benefit is the ability to register one template definition with
multiple template ids. This would allow routing messages based on
template id.In that case, why is the template id duplicated in the template
definition message?