RE: [Quickfix-developers] [qfj] Publishing Messages to JMS

[Steve B. <st...@te...>]

Hi Caleb,

I'm looking at the C++ Session code as I see the following
fragment for non-admin messages:

m_application.toApp( message, m_sessionID );
message.toString( messageString );
if ( isLoggedOn() )
    result =3D send( messageString );
}

It looks like the message is not passed to the send() method
if the session is not logged on. The send() method is where
the message is persisted. Am I interpreting this correctly?

Steve

________________________________________
From: Caleb Epstein [mailto:cal...@gm...]=20
Sent: Monday, September 12, 2005 10:46 AM
To: Steve Bate
Cc: qui...@li...
Subject: Re: [Quickfix-developers] [qfj] Publishing Messages to JMS

On 9/12/05, Steve Bate <st...@te...> wrote:
> Brad Harvey wrote:
> - If I start an initiator and send a message before the logon process =
is
> completed the message doesn't go anywhere.=A0=A0If I explicitly wait =
until
> the session is logged on then it works fine.=20

Is there a resend request after the logon? What is the expected behavior
of FIX when a message is sent before a session has been associated with
a connection? What does the C++ engine do in this case?

The C++ implementation always persists messages first, thereby assigning
them a sequence number, and then sends them (excepting of course =
resends).

So in the case that the conneciton is down when a message is sent by the
Application, it will be logged and resent as a PossDup once the =
connection
is re-established.=A0 The Application's first Logon message will have a =
higher
sequence number (e.g. 2) which will cause the counterparty to request a
resend, at which point the original message 1 will be resent.

--=20
Caleb Epstein
caleb dot epstein at gmail dot com=20