[This message was posted by Mahesh Kumaraguru of <kay_mah...@yahoo.com> 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/325c2a21 - PLEASE DO NOT REPLY BY MAIL.]
> > Hi Russ, > > > > We could use 95 RawDataLength and 96 RawData (Unformatted raw data, > > can include bitmaps, word processor documents, etc.) to transport > > MIME data. Presently 95 and 96 is only being used in Logon, these > > tags could be included in Message Type n and rename n XML_non_FIX > > to non_FIX > > > > Regards, Mahesh > > Hi Mahesh, > > Sure, but I guess what I'm getting at is there is no tag to specify the > actualy content-type of the message. I think we'd still need a message > type that identifies the data block as mime content... > > Cheers, > > Russ Hi Russ, You are right - A new message type to tell its a mime message, a new tag to identify the mime content type using the values listed under "Mime Types By File Extension" at http://www.w3schools.com/media/media_mimeref.asp and 95 RawDataLength and 96 RawData would contain the actual data itself. Cheers, Mahesh [You can unsubscribe from this discussion group by sending a message to mailto:unsubscribe+100932...@fixprotocol.org] -- You received this message because you are subscribed to the Google Groups "Financial Information eXchange" group. To post to this group, send email to fix-proto...@googlegroups.com. To unsubscribe from this group, send email to fix-protocol+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/fix-protocol?hl=en.
