Re: [Quickfix-developers] order of tags

[Alvin W. <AW...@FF...>]

Thanks.
Does tags of a component block need to be put together?  I think so...






Dave Linaker <dav...@ma...>
12/05/2005 05:43 PM

 
        To:     Alvin Wang <AW...@FF...>, Oren Miller <or...@qu...>, 
<qui...@li...>, 
<qui...@li...>
        cc: 
        bcc: 
        Subject:        Re: [Quickfix-developers] order of tags


Hi Alvin,

As far as I understand, the default ordering of tags is numeric, i.e. 
lowest tag number first and highest last. The header and trailer are 
slightly different, in that the header must start with tag 8, 9 and 35, 
and the trailer must end with tag 10, but otherwise tags are ordered 
numerically. 

With repeating groups order is more important and hence there is a 
constructor that allows you to specify a message order, e.g.:

    Group( int field, int delim, const int order[] )

...where order[] specifies the tag sort order.

The ordering seems to be implemented in FieldMap, a base class used for 
the various message parts.

Oren, Are there any thoughts on providing a similar constructor in the 
message class?

Dave


On 6/12/05 5:31 am, "Alvin Wang" <AW...@FF...> wrote:

Hi 

I wonder how the order of tags in a message is determined. It seems that 
it is not the same order that code sets the tags. If that is the case, how 
can I guarantee that all the tags belong to the same component block (such 
as Instrument component block) are put together in a message? 

Thanks 

Alvin 
********************************************************************** 
This e-mail message is intended solely for the use of the addressee. The 
message may contain information that is privileged and confidential. 
Disclosure to anyone other than the intended recipient is prohibited. If 
you are not the intended recipient, please do not disseminate, distribute 
or copy this communication, by e-mail or otherwise. Instead, please notify 
us immediately by return e-mail (including the original message with your 
reply) and then delete and discard all copies of the message. We have 
taken precautions to minimize the risk of transmitting software viruses 
but nevertheless advise you to carry out your own virus checks on any 
attachment to this message.  We accept no liability for any loss or damage 
caused by software viruses. 
**********************************************************************