|
4.3 Changes
< Previous Next >
re: sessions tests - 14g
Scott Atwell / American Century <>
21 Aug 2001 8:03AM ET The FIX 4.0 spec does state: "Each message, administrative or application, is preceded by a standard header." and somewhat contradictory "Except where noted, fields within a message can be defined in any sequence (i.e. relative position of a field within a record is inconsequential); exceptions are explicitly defined otherwise (certain header fields and fields within repeating data groups)."
The FIX 4.1 with Errata 19990630 spec corrected the somewhat contradictory 4.0 statement with: "Except where noted, fields within a message can be defined in any sequence (Relative position of a field within a record is inconsequential.) Any exceptions are explicitly defined otherwise: four header/trailer fields (BeginString, BodyLength, MsgType, and CheckSum), and fields within repeating data groups, and general message format of standard header followed by body followed by standard trailer."
Thus this is certainly not a "4.3-only test". One could argue either way re: 4.0, however, it's been clearly stated for the past 2+ years in 4.1, 4.2, and 4.3.
> The session level test (volume 2 of spec), 14g specifies that all header fields must preceed any body fields, etc., and requires a reject of any message with aberrant ordering; the test makes no exception for prior versions of the spec. Previous discussions have strongly indicated that such ordering was not specified or required in 4.0; it would seem dangerous to require rejection of such messages in a 4.0 session at this point. Maybe this should be a 4.3-only test.
>
re: sessions tests - 14g
Scott Atwell / American Century 21 Aug 2001 8:03AM ET
|
@FIXProtocol
