You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It's very common for FIX log files to be written with one message per line, and a direction (send/recv) and timestamp prior to the message.
It'd be nice if FixParser were able to parse such files "out of the box" without having to trim the lines manually first.
Add an optional FixParser behaviour to enable it to ignore spurious characters before the 8=FIX and after the 10=xxx|, such that it can read a FIX log file into a sequence of messages with a single call to append_buffer().
The text was updated successfully, but these errors were encountered:
It's very common for FIX log files to be written with one message per line, and a direction (send/recv) and timestamp prior to the message.
It'd be nice if
FixParser
were able to parse such files "out of the box" without having to trim the lines manually first.Add an optional
FixParser
behaviour to enable it to ignore spurious characters before the8=FIX
and after the10=xxx|
, such that it can read a FIX log file into a sequence of messages with a single call toappend_buffer()
.The text was updated successfully, but these errors were encountered: