[This message was posted by William Hooper of NA <[email protected]> to the "FAST Protocol" discussion forum at http://fixprotocol.org/discuss/46. You can reply to it on-line at http://fixprotocol.org/discuss/read/f27e08b0 - PLEASE DO NOT REPLY BY MAIL.]
I had a quick look at the documents you posted here: http://www.fastliteproposal.com/pub/FastLiteProposal-Draft-0-0-1.doc And just wanted to add my 2p of ideas... If I was to create a new format I would say: *Scrap the body length *Scrap the checksum length *Send times as int64 eg as microseconds since 01-jan-2000 *Scrap sendcomp id, target comp id, constant fields, Message Sequence Number and other fix stuff which are not needed for data feeds *Scrap heartbeats and logins from the client - only a test request is required *Limit the scope of the dictionary to the current template and have no global dictionary even for template id *Send a template id byte length so the user can skip templates he is not interest in and get an easy error check *Scrap optional fields, make delta fields work like others with bit in pmap *Add doubles to the sample application *Post a sample console app in c# /java with blocking sockets that sends messages back and forth With all that you have an easy to use general purpose data feed that works well enough I think. [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 -~----------~----~----~----~------~----~------~--~---
