protobuf encoding with FIX prtocol

[abdelrahman hamdy]

can anyone help me understanding this block of code and haw file have this value in the same line, example in FIX protocol tage = value so deliver companyID  tage=value is 128 = IBM for example.

i need help please .

 string deliver_to_comp_id = 3       [(fix.tag)=128, (fix.type)=DATATYPE_STRING, (fix.field_added)=VERSION_FIX_4_0];

message StandardHeader {

   string begin_string = 1             [(fix.tag)=8, (fix.type)=DATATYPE_STRING, (fix.field_added)=VERSION_FIX_4_0];

   sfixed64 body_length = 2            [(fix.tag)=9, (fix.type)=DATATYPE_LENGTH, (fix.field_added)=VERSION_FIX_4_0];

   string deliver_to_comp_id = 3       [(fix.tag)=128, (fix.type)=DATATYPE_STRING, (fix.field_added)=VERSION_FIX_4_0];

   string deliver_to_sub_id = 4        [(fix.tag)=129, (fix.type)=DATATYPE_STRING, (fix.field_added)=VERSION_FIX_4_0];

   sfixed64 msg_seq_num = 5            [(fix.tag)=34, (fix.type)=DATATYPE_SEQ_NUM, (fix.field_added)=VERSION_FIX_4_0];

   MsgTypeEnum msg_type = 6            [(fix.tag)=35, (fix.type)=DATATYPE_STRING, (fix.field_added)=VERSION_FIX_4_0];

   string on_behalf_of_comp_id = 7     [(fix.tag)=115, (fix.type)=DATATYPE_STRING, (fix.field_added)=VERSION_FIX_4_0];

   string on_behalf_of_sub_id = 8      [(fix.tag)=116, (fix.type)=DATATYPE_STRING, (fix.field_added)=VERSION_FIX_4_0];

   fix.Timestamp orig_sending_time = 9 [(fix.tag)=122, (fix.type)=DATATYPE_UTC_TIMESTAMP, (fix.field_added)=VERSION_FIX_4_0];

   bool poss_dup_flag = 10             [(fix.tag)=43, (fix.type)=DATATYPE_BOOLEAN, (fix.field_added)=VERSION_FIX_4_0];

   bool poss_resend = 11               [(fix.tag)=97, (fix.type)=DATATYPE_BOOLEAN, (fix.field_added)=VERSION_FIX_4_0];

   string secure_data = 12             [(fix.tag)=91, (fix.type)=DATATYPE_DATA, (fix.field_added)=VERSION_FIX_4_0];

   sfixed64 secure_data_len = 13       [(fix.tag)=90, (fix.type)=DATATYPE_LENGTH, (fix.field_added)=VERSION_FIX_4_0];

   string sender_comp_id = 14          [(fix.tag)=49, (fix.type)=DATATYPE_STRING, (fix.field_added)=VERSION_FIX_4_0];

   string sender_sub_id = 15           [(fix.tag)=50, (fix.type)=DATATYPE_STRING, (fix.field_added)=VERSION_FIX_4_0];

   fix.Timestamp sending_time = 16     [(fix.tag)=52, (fix.type)=DATATYPE_UTC_TIMESTAMP, (fix.field_added)=VERSION_FIX_4_0];

   string target_comp_id = 17          [(fix.tag)=56, (fix.type)=DATATYPE_STRING, (fix.field_added)=VERSION_FIX_4_0];

   string target_sub_id = 18           [(fix.tag)=57, (fix.type)=DATATYPE_STRING, (fix.field_added)=VERSION_FIX_4_0];

   string deliver_to_location_id = 19  [(fix.tag)=145, (fix.type)=DATATYPE_STRING, (fix.field_added)=VERSION_FIX_4_1];

   string on_behalf_of_location_id = 20                    [(fix.tag)=144, (fix.type)=DATATYPE_STRING, (fix.field_added)=VERSION_FIX_4_1];

   string sender_location_id = 21      [(fix.tag)=142, (fix.type)=DATATYPE_STRING, (fix.field_added)=VERSION_FIX_4_1];

   string target_location_id = 22      [(fix.tag)=143, (fix.type)=DATATYPE_STRING, (fix.field_added)=VERSION_FIX_4_1];

   sfixed64 last_msg_seq_num_processed = 23                [(fix.tag)=369, (fix.type)=DATATYPE_SEQ_NUM, (fix.field_added)=VERSION_FIX_4_2];

   string message_encoding = 24        [(fix.tag)=347, (fix.type)=DATATYPE_STRING, (fix.field_added)=VERSION_FIX_4_2];

   string xml_data = 25                [(fix.tag)=213, (fix.type)=DATATYPE_DATA, (fix.field_added)=VERSION_FIX_4_2];

   sfixed64 xml_data_len = 26          [(fix.tag)=212, (fix.type)=DATATYPE_LENGTH, (fix.field_added)=VERSION_FIX_4_2];

   ApplVerIDEnum appl_ver_id = 27      [(fix.tag)=1128, (fix.type)=DATATYPE_STRING, (fix.field_added)=VERSION_FIX_4_4];

   string cstm_appl_ver_id = 28        [(fix.tag)=1129, (fix.type)=DATATYPE_STRING, (fix.field_added)=VERSION_FIX_4_4];

   repeated HopGrp hop_grp = 29        [(fix.field_added)=VERSION_FIX_4_4];

   sfixed64 appl_ext_id = 30           [(fix.tag)=1156, (fix.type)=DATATYPE_INT, (fix.field_added)=VERSION_FIX_5_0];

}

[Marc Gravell]

That definition is simply adding metadata to the field definitions; they won't directly impact protobuf if you're using the default tools, but if you're using custom tools, or a layer on top of protobuf that knows how to inspect metadata, it can do additional things with the information. The metadata isn't part of *payload* data; it exists independent of any individual messages.

If you want more info, perhaps try clarifying the question so we understand which bit it unclear.

--
You received this message because you are subscribed to the Google Groups "Protocol Buffers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to protobuf+u...@googlegroups.com.
To post to this group, send email to prot...@googlegroups.com.
Visit this group at https://groups.google.com/group/protobuf.
To view this discussion on the web visit https://groups.google.com/d/msgid/protobuf/a1a8edb7-57eb-4a27-b1df-bfbbd29e4a88%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--

Regards,

Marc