Re: [Quickfix-developers] Multiple FIX acceptor servers

[Oren M. <or...@qu...>]

We will take a look at this.  I don't think it will make it to the next =
release, but we may put this or something like it into one of the =
following releases.

--oren
  ----- Original Message -----=20
  From: Pasquale d'Aloise=20
  To: qui...@li...=20
  Sent: Tuesday, May 17, 2005 12:41 PM
  Subject: [Quickfix-developers] Multiple FIX acceptor servers


  Hi,
  I have the need to start two FIX acceptors on two different machines =
letting an initiator connect alternatively to both ones. This scenario =
is useful to implement fault-tolerant services.

  With the current release of QuickFIX library (1.9.4) I have the =
problem of maintaining the sequence numbers synchronized, even if I use =
the database storing; QuickFIX, in fact, keeps an internal copy of =
sequence numbers that it uses to validate the incoming messages and to =
set the outgoing ones.

  So I have worked around the problem by adding the virtual method =
ReloadSeqNums() to the class MessageStore and to its derived MySQLStore. =
The MySQLStore implementation of this method is:

      void MySQLStore::ReloadSeqNums() { populateCache(); }

  I call the above mentioned method in void Session::nextLogon( const =
Message& logon ) by means of the following statement:

      m_state.store()->ReloadSeqNums();

  Do you think this update could be extended to future versions of the =
QuickFIX library?
  If you have any concerns about my update, please let me know.

  Regards,
  Pasquale d'Aloise
  GATE Tecnologie Informatiche s.r.l.