[This message was posted by Hanno Klein of Deutsche Börse Systems <[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/16812834 - PLEASE DO NOT REPLY BY MAIL.]
If FPL were to do this, then there is hardly a reason ever to move away from FIX 4.2. The FIX spec is not a piece of software but it seems to be the only versioned object where there is a strong desire to extend the capabilities without changing the version number. FIX 4.2 will be 10 years old in less than half a year. In my view it is becoming more of a marketing label than a reflection of what it offers. People have real needs to extend their functionality but assume that a move to FIX 5 is a major step. It is much less of an effort if you look into the details. Here is a way out for you: use tag 6391 or 6614 or 9904. They are all called "PriceType" and might fit your needs and will not be rejected by a standard FIX engine. There are about 10 more user-defined tags with the term "PriceType" in them that might also qualify. > Would it be a terrible idea to just return PriceType with the > SecurityDefinition as an added field for FIX4.2 clients? I don't really > want to force clients to use FIX5.0 and I also don't want someone to > submit an order thinking he is specifying price when we are expecting > yield. Right now the plan is to require the PriceType be set in the > NewOrderSingle message and if the type does not match the expected type > we reject the order and the OrdRejReason text field will supply the > proper PriceType, but of course that is less than ideal since the client > has no reasonable way to divine what PriceType we expect except by > assuming conventional pricing. > [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]. For more options, visit this group at http://groups.google.com/group/fix-protocol?hl=.
