[This message was posted by Mahesh Kumaraguru of <[email protected]> to the "General Q/A" discussion forum at http://fixprotocol.org/discuss/22. You can reply to it on-line at http://fixprotocol.org/discuss/read/9fa4da31 - PLEASE DO NOT REPLY BY MAIL.]
Hi Russ, Jim, By adding a new enumerated tag to identify the content type, we can make 35=n transmit XML, MIME, RawData or other contents in the future by extending the enumeration. The enumeration for this NewTag could be 1 - XML 2 - MIME 3 - RawData When the value of NewTag = 1, then XMLDataLen(212) and XMLData(213) would become conditionally required. When the value of NewTag = 2 or 3, then RawDataLength(95) and RawData(96) would become conditionally required. Based on this value the receiving application would know whether to parse RawData as MIME or RawData itself. Being able to transmit RawData would be useful for integrators who want to replace a non FIX session which exchanges String messages with FIXT session which would not use FIX itself. Regards, K. Mahesh [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.
