[This message was posted by Richard Labs of CL&B Capital Management, LLC <[email protected]> to the "Algorithmic Trading" discussion forum at http://fixprotocol.org/discuss/31. You can reply to it on-line at http://fixprotocol.org/discuss/read/79033a60 - PLEASE DO NOT REPLY BY MAIL.]
> Why are two boolean parameters mutableOnCxlRpl and revertOnCxlRpl needed > if mutableOnCxlRpl = True THEN revertOnCxlRpl = False and vice versa ? > Could not the logic be represented by a single boolean parameter ? Yes, if above were true, in absolutely every single use-case, we would be good to go with one Boolean parameter. Things are designed a bit "loose" in FIXatdl on occasion to accommodate some very wide actual standing commercial implementations of cancel/replace. In areas were some players in the industry itself "got off the path" a bit from the strict FIX Protocol recommended approach, particularly if that narrow approach evolved over time, we at FIXatdl didn't force (or assume) tight compliance. We tried not to break things that were already in use. Some of the stuff that seems "extra" or is marked " Deprecated " is to allow the few odd use-cases we had in front of us that we didn't want to break. Might encourage FIX to formally review cancel/replace technology and try to narrow industry usage / semantics / understandings. However that effort would have to be outside FIXatdl and FIXatdl would just run with the the results. Same for date/time/event handling and a few other areas that still have some industry wide "looseness" in implementation. [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.
