[This message was posted by Russell Curry of Assimilate Technology, Inc. <r...@assimilate.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/fe77dbef - PLEASE DO NOT REPLY BY MAIL.]
> 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 Hi Mahesh, Right - actually, we wouldn't even need a new tag, since the MIME type(s) can be specified in the actual payload, the same way they are in HTTP or in an email message. All this would take is to declare a MIME message type and, for the sake of formality, registering the various new types, like FIXML or FPML, with IANA as proper MIME types... It's a simple improvement, but I think this would add quite a bit to FIXT's usefulness as a multi-purpose transport protocol for financial applications. [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.
