[Quickfix-users] Logon with ResetSeqNumFlag and BOX

[<Ark...@ub...>]

Hello All!

I am using QuickFix to connect to BOX (http://www.bostonoptions.com/). I =
am using version 1.10.2 of QuickFix, so I am able to request a session =
reset by setting ResetSeqNumFlag  in my logon message (thank you for =
this feature!). However, I see an interesting snag. BOX responds with =
its own Logon message, but in the response, BOX does not set the =
ResetSeqNumFlag flag. QuickFix exepects the flag to be set, otherwise =
the logon response is treated as logon request:

>>>>>>>>>>>>>>> Session.cpp:220
  if ( !m_state.initiate()=20
       || (m_state.sentReset() && !m_state.receivedReset()) )
  {
    if( logon.isSetField(m_state.heartBtInt()) )
      logon.getField( m_state.heartBtInt() );
    m_state.onEvent( "Received logon request" );
    generateLogon( logon );
    m_state.onEvent( "Responding to logon request" );
  }
<<<<<<<<<<<<<<<


So I get to send another logon, and then another. Since I only set =
ResetSeqNumFlag in the original Logon message, the session eventually =
settles down, after sending 3 logons and receiving 1 response.

Would it be possible to either treat logon response with seq number 1 as =
if it has ResetSeqNumFlag? Or may be let me add the flag in =
Application::fromAdmin (as it is now, Application::fromAdmin is called =
after the check for ResetSeqNumFlag is done.


Sincerely,
		Arkadiy Belousov.






Visit our website at http://www.ubs.com

This message contains confidential information and is intended only 
for the individual named.  If you are not the named addressee you 
should not disseminate, distribute or copy this e-mail.  Please 
notify the sender immediately by e-mail if you have received this 
e-mail by mistake and delete this e-mail from your system.

E-mail transmission cannot be guaranteed to be secure or error-free 
as information could be intercepted, corrupted, lost, destroyed, 
arrive late or incomplete, or contain viruses.  The sender therefore 
does not accept liability for any errors or omissions in the contents 
of this message which arise as a result of e-mail transmission.  If 
verification is required please request a hard-copy version.  This 
message is provided for informational purposes and should not be 
construed as a solicitation or offer to buy or sell any securities or 
related financial instruments.