[Quickfix-developers] Apparent session logout logic problem

[Gene G. <mus...@ya...>]

Please forgive me if I am wildly off the mark, but
should not the session be completely reset, including
the target session num and file store, upon receiving
a logout message? 
I have been testing QuickFIX interoperability with
another engine using the ordermatch sample, and their
test client keeps getting rejected on sessions after
the first one, because it resets the msgnum back to 1
after sending a valid logout, and QuickFIX does not 
That another vendor, which I cannot disclose, keeps
separate message counters for every login/logout pair.
In my view their approach corresponds better to FIX
specification, which clearly indicates that logout
message terminates session, nd therefore sequence
numbers ought to be restarted.
If I am right and this is indeed a problem, the quick
and dirty way to change the behavior would be to
perform a Session::reset() instead of
Session::disconnect() when a logout message is
received.

Gene Gorokhovsky


__________________________________________________
Do You Yahoo!?
Sign up for SBC Yahoo! Dial - First Month Free
http://sbc.yahoo.com