quickfix-users — QuickFIX user support

Re: [Quickfix-users] compiling error

[Joerg T. <Joe...@ma...>]

> I am trying to compile on a linux 2.4.19 i686 machine with gcc version
> 3.0.4. Running configure works correctly but I get the error
> 
> /usr/bin/ld: cannot find -lquickfix
> 
> when I run make.
> 
> Am I doing something wrong or missing a step? All I did was
> ./configure
> make

Which version of QuickFIX do you use?
Perhaps you could provide some output from make or configure? Did you 
try to do

./bootstrap

before running ./configure?

Jo"rg

-- 
Joerg Thoennes
                                http://macd.com
Tel.: +49 (0)241 44597-24      Macdonald Associates GmbH
Fax : +49 (0)241 44597-10      Lothringer Str. 52, D-52070 Aachen

Re: [Quickfix-users] compiling error

[Oren M. <ore...@ya...>]

Can you show the context in which you get that error? 
If you can post a larget sample of your make output,
that would be more helpful.

--- Alex <ax...@m-...> wrote:
> I am trying to compile on a linux 2.4.19 i686
> machine with gcc version
> 3.0.4. Running configure works correctly but I get
> the error
> 
> /usr/bin/ld: cannot find -lquickfix
> 
> when I run make.
> 
> Am I doing something wrong or missing a step? All I
> did was
> ./configure
> make
> 
> Thanks.
> 
> 
> 
> 
> 
>
-------------------------------------------------------
> This SF.Net email sponsored by: Parasoft
> Error proof Web apps, automate testing & more.
> Download & eval WebKing and get a free book.
> www.parasoft.com/bulletproofapps1
> _______________________________________________
> Quickfix-users mailing list
> Qui...@li...
> https://lists.sourceforge.net/lists/listinfo/quickfix-users

__________________________________
Do you Yahoo!?
SBC Yahoo! DSL - Now only $29.95 per month!
http://sbc.yahoo.com

[Quickfix-users] compiling error

[Alex <ax...@m-...>]

I am trying to compile on a linux 2.4.19 i686 machine with gcc version
3.0.4. Running configure works correctly but I get the error

/usr/bin/ld: cannot find -lquickfix

when I run make.

Am I doing something wrong or missing a step? All I did was
./configure
make

Thanks.

RE: [Quickfix-users] What is correct behavior if sender has error sending msg?

[Oren M. <ore...@ya...>]

Well gaps in the message store are perfectly normal.  QF only stores messages that can be resent (i.e., application messages).  So messages like heartbeats for instance do not get stored.  You should check your log file to verify that the message gap is caused by some administrative message, which is expected behavior. Message gaps in the filestore won't cause a problem because QF will just insert SequenceReset/Gap Fill messages during a resend.

"Brendan B. Boerner" <br...@ka...> wrote:Oren,

Thanks for the reply. Comments below.

> -----Original Message-----
> From: Oren Miller [mailto:ore...@ya...]

> m_state.set( msgSeqNum, messageString );
> m_state.incrNextSenderMsgSeqNum();
>
> This is ok whether or not the send is succesful,
> because the message will be resent sometime in the
> future. When send returns true, it actually isn't

This is done when an attempt to send another msg occurs or in the
background?

> terribly informative since it really could be
> logically false. It is true if we send on the socket
> and it returns false we know it failed, but if it
> returns true, at best we think it likely succeeded but
> maybe not. This is because we don't know if the
> counterparty processed it and is as good as not sent.
> So the success of any particular send doesn't really
> matter in the context of post processing.
>
> In fact, some people have pointed out recently
> (rightfully) that storage should be done *before* we
> even attempt to send. And if we store and increment
> before sending, then the irrelevancy of that return
> value becomes more clear.
>
> Did you experience a particular problem with this?

Yes, but now that I'm trying to reproduce it, I can't :-(.

What I was seeing were 'gaps' in the message store e.g.

8=FIX.4.1^A9=60^A35=2^A34=100^A49=CLYN7^A52=20030711-20:08:00^A56=SLK^A7=87^
A16=91^A10=165^A
8=FIX.4.1^A9=60^A35=2^A34=101^A49=CLYN7^A52=20030711-20:08:00^A56=SLK^A7=87^
A16=92^A10=167^A
8=FIX.4.1^A9=60^A35=2^A34=103^A49=CLYN7^A52=20030711-20:08:00^A56=SLK^A7=87^
A16=94^A10=171^A
8=FIX.4.1^A9=60^A35=2^A34=104^A49=CLYN7^A52=20030711-20:08:00^A56=SLK^A7=87^
A16=95^A10=173^A

which would cause the target to issue a resend request. Since it
couldn't be honored the target wouldn't allow further processing (I'm
pretty sure that the Sender didn't issue a Sequence Reset in this
case either).

Next time I can reproduce I'll debug further.

Regards,
Brendan





---------------------------------
Do you Yahoo!?
SBC Yahoo! DSL - Now only $29.95 per month!

RE: [Quickfix-users] What is correct behavior if sender has error sending msg?

[Brendan B. B. <br...@ka...>]

> From: Brendan Boerner
> > From: Oren Miller [mailto:ore...@ya...]

> > Did you experience a particular problem with this?

> Yes, but now that I'm trying to reproduce it, I can't <grrrr> :-(.
> 
> What I was seeing were 'gaps' in the message store e.g.
> 
> 8=FIX.4.1^A9=60^A35=2^A34=100^A49=CLYN7^A52=20030711-20:08:00^A56=
> SLK^A7=87^
> A16=91^A10=165^A
> 8=FIX.4.1^A9=60^A35=2^A34=101^A49=CLYN7^A52=20030711-20:08:00^A56=
> SLK^A7=87^
> A16=92^A10=167^A
> 8=FIX.4.1^A9=60^A35=2^A34=103^A49=CLYN7^A52=20030711-20:08:00^A56=
> SLK^A7=87^
> A16=94^A10=171^A
> 8=FIX.4.1^A9=60^A35=2^A34=104^A49=CLYN7^A52=20030711-20:08:00^A56=
> SLK^A7=87^
> A16=95^A10=173^A
> 
> which would cause the target to issue a resend request.  Since it
> couldn't be honored the target wouldn't allow further processing (I'm
> pretty sure that the Sender didn't issue a Sequence Reset in this
> case either).
> 
> Next time I can reproduce I'll debug further.

Ok, I can see it occur and have more insight into the problem.

bool Session::sendRaw( Message& message, int num )
{
    ...
    if ( isLoggedOn() )
      result = send( message.toString(messageString) );
    if ( !num )
    {
      MsgSeqNum msgSeqNum;
      header.getField( msgSeqNum );
      m_state.set( msgSeqNum, messageString );
      m_state.incrNextSenderMsgSeqNum();
    }
    ...
}    

The problem is occuring because isLoggedOn() is returning false (I
see this most when I've had my client paused in the debugger for a
bit - this is to be expected if the server wasn't getting any
heartbeats from the client.  I *think* I've also seen it when I slam
> 50 orders at once right after getting a notification of
Application::onLogon(). I haven't debugged into this much).

Since messageString is constructed in the call to send(),
m_state.set( msgSeqNum, messageString ) will attempt to write a ""
string to the store, thus the gap.

What's weird is that modifying it to be:
    message.toString(messageString);
    if ( isLoggedOn() )
      result = send(messageString);

still results in nothing being written to the store!

I've traced into FileStore::set( int msgSeqNum, const std::string&
msg ) and fwrite() is getting a valid message to write but it's not
showing up in the file.  I know this is occuring when I've created
the problem when sending > 50 orders right after I've logged on, I
don't know if the problem exists when I've logged off due to sitting
in the debugger.

Question: If not logged on, do we really want to queue messages?

Suppose (to construct a contrived scenario) that the app sends an
order to buy 1000 contracts of FOOBAR @ mkt where mkt is X.  The
connection is down for whatever reason for a significant length of
time.  The app is coded to issue a cancel if it doesn't get an order
ack within some amount of time which is also queued.

When the connection comes back up, the NewOrderSingle is sent out
followed by the OrderRequestCancel.  If the FIX server enforces logic
that an OrderRequestCancel won't be honored until the NewOrderSingle
is ACKed, the NewOrderSingle will have to enter the mkt in some
fashion and the app will need to resend the OrderRequestCancel.

If the mkt has moved significantly away from X in the interval that
the link was down, the order could be filled at a price which could
be detrimental to the person(s) funding the account...

It seems to me that if the message is not queued if not logged on,
the app can check the result from sendToTarget(), know the order
wasn't sent and retry (or not) until it makes it through.

Regards,
Brendan

[Quickfix-users] Session::doTargetTooLow throws before printing onEvent msg if possDupFlag not present

[Brendan B. B. <br...@ka...>]

Hello,

In bool Session::doTargetTooLow( const Message& msg ), is the
possDupFlag is not set, a FieldNotFound exception will be thrown on:

header.getField( possDupFlag );

This will prevent m_state.onEvent() from being called and displaying
the problem.

If one were to do a

if ( header.isSetField( possDupFlag ) ) header.getField( possDupFlag );

Then the call to BoolConvertor::convert( possDupFlag ) would throw.

Since
  if ( !possDupFlag )
    throw std::exception();

at the end will throw *after* the message is printed, would this be
the right fix:

bool Session::doTargetTooLow( const Message& msg )
{ QF_STACK_PUSH(Session::doTargetTooLow)

  const Header & header = msg.getHeader();
  MsgType msgType;
//#define ORIG  1
#if ORIG
  // brendan; 7/11: onEvent Msg won't be printed if possDupFlag isn't
present in message
  PossDupFlag possDupFlag(false);
#else
  PossDupFlag possDupFlag();
#endif // #if ORIG
  MsgSeqNum msgSeqNum;
  header.getField( msgType );
#if ORIG
  // brendan; 7/11: onEvent Msg won't be printed if possDupFlag isn't
present in message
  if ( header.isSetField( possDupFlag ) ) header.getField( possDupFlag );
#else
  header.getField( possDupFlag );
#endif // #if ORIG
  header.getField( msgSeqNum );

  m_state.onEvent( "MsgSeqNum too low RECEIVED: "
                   + IntConvertor::convert( msgSeqNum )
                   +" EXPECTED: "
                   + IntConvertor::convert( getExpectedTargetNum() )
                   + " PosDup: " + BoolConvertor::convert( possDupFlag ) );

  if ( !possDupFlag )
    throw std::exception();
  return doPossDup( msg );

  QF_STACK_POP
}

?

Regards,
Brendan

RE: [Quickfix-users] What is correct behavior if sender has error sending msg?

[Brendan B. B. <br...@ka...>]

Oren,

Thanks for the reply.  Comments below.

> -----Original Message-----
> From: Oren Miller [mailto:ore...@ya...]

> m_state.set( msgSeqNum, messageString );
> m_state.incrNextSenderMsgSeqNum();
>
> This is ok whether or not the send is succesful,
> because the message will be resent sometime in the
> future.  When send returns true, it actually isn't

This is done when an attempt to send another msg occurs or in the
background?

> terribly informative since it really could be
> logically false.  It is true if we send on the socket
> and it returns false we know it failed, but if it
> returns true, at best we think it likely succeeded but
> maybe not.  This is because we don't know if the
> counterparty processed it and is as good as not sent.
> So the success of any particular send doesn't really
> matter in the context of post processing.
>
> In fact, some people have pointed out recently
> (rightfully) that storage should be done *before* we
> even attempt to send.  And if we store and increment
> before sending, then the irrelevancy of that return
> value becomes more clear.
>
> Did you experience a particular problem with this?

Yes, but now that I'm trying to reproduce it, I can't <grrrr> :-(.

What I was seeing were 'gaps' in the message store e.g.

8=FIX.4.1^A9=60^A35=2^A34=100^A49=CLYN7^A52=20030711-20:08:00^A56=SLK^A7=87^
A16=91^A10=165^A
8=FIX.4.1^A9=60^A35=2^A34=101^A49=CLYN7^A52=20030711-20:08:00^A56=SLK^A7=87^
A16=92^A10=167^A
8=FIX.4.1^A9=60^A35=2^A34=103^A49=CLYN7^A52=20030711-20:08:00^A56=SLK^A7=87^
A16=94^A10=171^A
8=FIX.4.1^A9=60^A35=2^A34=104^A49=CLYN7^A52=20030711-20:08:00^A56=SLK^A7=87^
A16=95^A10=173^A

which would cause the target to issue a resend request.  Since it
couldn't be honored the target wouldn't allow further processing (I'm
pretty sure that the Sender didn't issue a Sequence Reset in this
case either).

Next time I can reproduce I'll debug further.

Regards,
Brendan

Re: [Quickfix-users] What is correct behavior if sender has error sending msg?

[Oren M. <ore...@ya...>]

If the send on the socket fails, that's ok.  It just
means that QF wasn't able to send the message
immediately.  At the bootom you will see that the
message is placed in the store and then the sessions
sequence number is incremented after storage (not
before):

m_state.set( msgSeqNum, messageString );
m_state.incrNextSenderMsgSeqNum();

This is ok whether or not the send is succesful,
because the message will be resent sometime in the
future.  When send returns true, it actually isn't
terribly informative since it really could be
logically false.  It is true if we send on the socket
and it returns false we know it failed, but if it
returns true, at best we think it likely succeeded but
maybe not.  This is because we don't know if the
counterparty processed it and is as good as not sent. 
So the success of any particular send doesn't really
matter in the context of post processing.

In fact, some people have pointed out recently
(rightfully) that storage should be done *before* we
even attempt to send.  And if we store and increment
before sending, then the irrelevancy of that return
value becomes more clear.

Did you experience a particular problem with this?
--- "Brendan B. Boerner" <br...@ka...>
wrote:
> Hello,
> 
> In bool Session::sendRaw( Message& message, int num
> ) it calls
> 
> --> Session::fill( Header& header ) which calls
>     --> header.setField( MsgSeqNum(
> getExpectedSenderNum() ) );
> 
> to set the Sender's MsgSeqNum of this msg to be sent
> to the target.
> 
> Then calling
> 
> --> std::string& Message::toString( std::string& str
> ) const which calls
>     --> bool Session::send( const std::string string
> ) which calls
>         --> bool SocketConnection::send( const
> std::string& msg ) which
> calls
>             --> bool socket_send( int s, const char*
> msg, int length )
> 
> which Returns true for no error, false otherwise.
> 
> Percolating back up to Session::sendRaw(), this
> results in
>    result = send( message.toString(messageString) );
> result being false if an error occured sending the
> message.
> 
> There's no check however in Session::sendRaw() if
> there was an error
> so the SenderMsgSeqNum remains incremented yet this
> message is not
> logged to the store.  When a connection is
> reestablished the target
> will issue Resend requests for the Msgs w/MsgSeqNum
> which weren't
> sent.  Since they weren't sent (and thus weren't
> logged) those
> request aren't honored.
> 
> I haven't debugged further to see if the Sender
> should be generating
> a Sequence Reset in this case (should it?) but would
> an acceptable
> response be to reset the Sender MsgSeqNum back to
> the value prior to
> the failed call e.g. in Session::sendRaw():
> 
> bool Session::sendRaw( Message& message, int num )
> {
>    ...
>    result = send( message.toString(messageString) );
> 
>     // brendan, 7/11: If socket error, Reset
> Sender's MsgSeqNum to
>     // prevent sequence # gaps.  Not doing so will
> cause Target's request to
>     // fill gaps w/Resend Request to fail (as
> messages not sent aren't
>     // logged to the store).
> #if ORIG
>     if ( !num )
>     {
>       MsgSeqNum msgSeqNum;
>       header.getField( msgSeqNum );
>       m_state.set( msgSeqNum, messageString );
>       m_state.incrNextSenderMsgSeqNum();
>     }
> #else
>     MsgSeqNum msgSeqNum;
>     if ( result )
>     {
>       if ( !num )
>       {
>         header.getField( msgSeqNum );
>         m_state.set( msgSeqNum, messageString );
>         m_state.incrNextSenderMsgSeqNum();
>       }
>     }
>     else
>     {
>       // reset msg seq num to prevent gaps
>       header.getField( msgSeqNum );
>       setNextSenderMsgSeqNum( msgSeqNum );
>     } /* end if-else */
> #endif // #if ORIG
> 
>   ...
> }
> 
> ?
> 
> Regards,
> Brendan
> 
> 
> 
> 
>
-------------------------------------------------------
> This SF.Net email sponsored by: Parasoft
> Error proof Web apps, automate testing & more.
> Download & eval WebKing and get a free book.
> www.parasoft.com/bulletproofapps1
> _______________________________________________
> Quickfix-users mailing list
> Qui...@li...
> https://lists.sourceforge.net/lists/listinfo/quickfix-users

__________________________________
Do you Yahoo!?
SBC Yahoo! DSL - Now only $29.95 per month!
http://sbc.yahoo.com

[Quickfix-users] What is correct behavior if sender has error sending msg?

[Brendan B. B. <br...@ka...>]

Hello,

In bool Session::sendRaw( Message& message, int num ) it calls

--> Session::fill( Header& header ) which calls
    --> header.setField( MsgSeqNum( getExpectedSenderNum() ) );

to set the Sender's MsgSeqNum of this msg to be sent to the target.

Then calling

--> std::string& Message::toString( std::string& str ) const which calls
    --> bool Session::send( const std::string string ) which calls
        --> bool SocketConnection::send( const std::string& msg ) which
calls
            --> bool socket_send( int s, const char* msg, int length )

which Returns true for no error, false otherwise.

Percolating back up to Session::sendRaw(), this results in
   result = send( message.toString(messageString) );
result being false if an error occured sending the message.

There's no check however in Session::sendRaw() if there was an error
so the SenderMsgSeqNum remains incremented yet this message is not
logged to the store.  When a connection is reestablished the target
will issue Resend requests for the Msgs w/MsgSeqNum which weren't
sent.  Since they weren't sent (and thus weren't logged) those
request aren't honored.

I haven't debugged further to see if the Sender should be generating
a Sequence Reset in this case (should it?) but would an acceptable
response be to reset the Sender MsgSeqNum back to the value prior to
the failed call e.g. in Session::sendRaw():

bool Session::sendRaw( Message& message, int num )
{
   ...
   result = send( message.toString(messageString) );

    // brendan, 7/11: If socket error, Reset Sender's MsgSeqNum to
    // prevent sequence # gaps.  Not doing so will cause Target's request to
    // fill gaps w/Resend Request to fail (as messages not sent aren't
    // logged to the store).
#if ORIG
    if ( !num )
    {
      MsgSeqNum msgSeqNum;
      header.getField( msgSeqNum );
      m_state.set( msgSeqNum, messageString );
      m_state.incrNextSenderMsgSeqNum();
    }
#else
    MsgSeqNum msgSeqNum;
    if ( result )
    {
      if ( !num )
      {
        header.getField( msgSeqNum );
        m_state.set( msgSeqNum, messageString );
        m_state.incrNextSenderMsgSeqNum();
      }
    }
    else
    {
      // reset msg seq num to prevent gaps
      header.getField( msgSeqNum );
      setNextSenderMsgSeqNum( msgSeqNum );
    } /* end if-else */
#endif // #if ORIG

  ...
}

?

Regards,
Brendan

[Quickfix-users] SocketConnection::read( SocketConnector& s ) doesn't catch RecvFailed exception

[Brendan B. B. <br...@ka...>]

Resending as I didn't see this in the archives so I don't know if it
made it out...

Regards,
Brendan

-----Original Message-----
From: qui...@li...
[mailto:qui...@li...]On Behalf Of Brendan
B. Boerner
Sent: Wednesday, July 09, 2003 8:09 AM
To: Quickfix-Users
Subject: [Quickfix-users] SocketConnection::read( SocketConnector& s )
doesn't catch RecvFailed exception


Hello,

bool SocketConnection::readMessage( std::string& msg ) calls
m_parser.readFixMessage( msg ); which calls Parser::readFromStream()
which can throw a RecvFailed exception.

Callers of SocketConnection::readMessage(...) are:

bool SocketConnection::read( SocketAcceptor& a, SocketServer& s )
bool SocketConnection::read( SocketConnector& s )
void ThreadedSocketConnection::processStream()

Only SocketConnection::read( SocketAcceptor& a, SocketServer& s )
catches the exception:

  catch ( RecvFailed& )
  {
    s.getMonitor().drop( m_socket );
  }


Shouldn't SocketConnection::read( SocketConnector& s ) (and
ThreadedSocketConnection::processStream(), I haven't used it) do
something similar e.g.

bool SocketConnection::read( SocketConnector& s )
{ QF_STACK_PUSH(SocketConnection::read)

#if 1
  // brendan 7/9/03
  if ( !m_pSession ) return false;

  std::string msg;
  try
  {
    if ( !readMessage( msg ) ) return false;
    m_pSession->next( msg );
  }
  catch ( InvalidMessage& )
  {
    return false;
  }
  catch ( RecvFailed& )
  {
    if ( !m_pSession->isLoggedOn() )
      s.getMonitor().drop( m_socket );
    return false;
  }

  return true;

#else
  // orig
  if ( !m_pSession ) return false;

  std::string msg;
  if ( !readMessage( msg ) ) return false;

  try
  {
    m_pSession->next( msg );
  }
  catch ( InvalidMessage& ) {}
  return true;
#endif // #if 1

  QF_STACK_POP
}

?

I don't think this is a complete fix - when I've been able to cause
the exception to be thrown and then let it go VC++ then proceeds to
take 50-90% CPU.  The only way I've been able to get out of that
state is to terminate the MSDEV.EXE process using TaskMan.

Regards,
Brendan



-------------------------------------------------------
This SF.Net email sponsored by: Parasoft
Error proof Web apps, automate testing & more.
Download & eval WebKing and get a free book.
www.parasoft.com/bulletproofapps
_______________________________________________
Quickfix-users mailing list
Qui...@li...
https://lists.sourceforge.net/lists/listinfo/quickfix-users

[Quickfix-users] SocketConnection::read( SocketConnector& s ) doesn't catch RecvFailed exception

[Brendan B. B. <br...@ka...>]

Hello,

bool SocketConnection::readMessage( std::string& msg ) calls
m_parser.readFixMessage( msg ); which calls Parser::readFromStream()
which can throw a RecvFailed exception.

Callers of SocketConnection::readMessage(...) are:

bool SocketConnection::read( SocketAcceptor& a, SocketServer& s )
bool SocketConnection::read( SocketConnector& s )
void ThreadedSocketConnection::processStream()

Only SocketConnection::read( SocketAcceptor& a, SocketServer& s )
catches the exception:

  catch ( RecvFailed& )
  {
    s.getMonitor().drop( m_socket );
  }


Shouldn't SocketConnection::read( SocketConnector& s ) (and
ThreadedSocketConnection::processStream(), I haven't used it) do
something similar e.g.

bool SocketConnection::read( SocketConnector& s )
{ QF_STACK_PUSH(SocketConnection::read)

#if 1
  // brendan 7/9/03
  if ( !m_pSession ) return false;

  std::string msg;
  try
  {
    if ( !readMessage( msg ) ) return false;
    m_pSession->next( msg );
  }
  catch ( InvalidMessage& )
  {
    return false;
  }
  catch ( RecvFailed& )
  {
    if ( !m_pSession->isLoggedOn() )
      s.getMonitor().drop( m_socket );
    return false;
  }

  return true;

#else
  // orig
  if ( !m_pSession ) return false;

  std::string msg;
  if ( !readMessage( msg ) ) return false;

  try
  {
    m_pSession->next( msg );
  }
  catch ( InvalidMessage& ) {}
  return true;
#endif // #if 1

  QF_STACK_POP
}

?

I don't think this is a complete fix - when I've been able to cause
the exception to be thrown and then let it go VC++ then proceeds to
take 50-90% CPU.  The only way I've been able to get out of that
state is to terminate the MSDEV.EXE process using TaskMan.

Regards,
Brendan

RE: [Quickfix-users] Re: [Quickfix-developers] FIXML Support

[Vamsi K. <Vam...@ib...>]

Oren
I  would  like  to  do that( Convert QuickFIX  message  object  into
FIXML  using  DataDictionary  and  a  transform).

Where do  I  think  I can  begin with ? I know  little of  XSLT.

I might as well contribute  my work to Quikfix..

Vamsi

/-----Original Message-----
/From: qui...@li...
[mailto:quickfix-users-
/ad...@li...] On Behalf Of Oren Miller
/Sent: Monday, July 07, 2003 4:07 PM
/To: Vamsi Krishna; qui...@li...; 'quickfix-
/developers'
/Subject: [Quickfix-users] Re: [Quickfix-developers] FIXML Support
/
/Well you can't really translate the QuickFIX data
/dictionary into a FIXML message.  The DataDictionary
/contains no actual field values and has multiple
/messages. Do you want to convert a QuickFIX message
/object into FIXML using the DataDictionary and a
/transform?
/
/--- Vamsi Krishna <Vam...@ib...> wrote:
/> Hi all
/> I know this question has been raised earlier. Will
/> Quickfix come up with
/> the Translation tool to convert its proprietary XML
/> form of FIX message
/> to "Official" FIXML message.
/>
/> I don't know XSLT and I would appreciate if somebody
/> comes up with a
/> sample program (XSLT) to make this translation
/> possible. I would in turn
/> contribute to QuickfIX group by programming the
/> entire message set.
/>
/> I have requirement to this regard from my client.
/> Also I would like to
/> whether XMLField is supported in QuickFIX.
/>
/> Any help is appreciated
/>
/> Vamsi
/>
/>
/>
/>
/-------------------------------------------------------
/> This SF.Net email sponsored by: Free pre-built
/> ASP.NET sites including
/> Data Reports, E-commerce, Portals, and Forums are
/> available now.
/> Download today and enter to win an XBOX or Visual
/> Studio .NET.
/>
/http://aspnet.click-url.com/go/psa00100006ave/direct;at.asp_061203_01/0
1
/> _______________________________________________
/> Quickfix-developers mailing list
/> Qui...@li...
/>
/https://lists.sourceforge.net/lists/listinfo/quickfix-developers
/
/
/__________________________________
/Do you Yahoo!?
/SBC Yahoo! DSL - Now only $29.95 per month!
/http://sbc.yahoo.com
/
/
/-------------------------------------------------------
/This SF.Net email sponsored by: Free pre-built ASP.NET sites including
/Data Reports, E-commerce, Portals, and Forums are available now.
/Download today and enter to win an XBOX or Visual Studio .NET.
/http://aspnet.click-url.com/go/psa00100006ave/direct;at.asp_061203_01/0
1
/_______________________________________________
/Quickfix-users mailing list
/Qui...@li...
/https://lists.sourceforge.net/lists/listinfo/quickfix-users

[Quickfix-users] Re: [Quickfix-developers] FIXML Support

[Oren M. <ore...@ya...>]

Well you can't really translate the QuickFIX data
dictionary into a FIXML message.  The DataDictionary
contains no actual field values and has multiple
messages. Do you want to convert a QuickFIX message
object into FIXML using the DataDictionary and a
transform?

--- Vamsi Krishna <Vam...@ib...> wrote:
> Hi all
> I know this question has been raised earlier. Will
> Quickfix come up with
> the Translation tool to convert its proprietary XML
> form of FIX message
> to "Official" FIXML message.
> 
> I don't know XSLT and I would appreciate if somebody
> comes up with a
> sample program (XSLT) to make this translation
> possible. I would in turn
> contribute to QuickfIX group by programming the
> entire message set.
> 
> I have requirement to this regard from my client.
> Also I would like to
> whether XMLField is supported in QuickFIX.
> 
> Any help is appreciated
> 
> Vamsi
> 
> 
> 
>
-------------------------------------------------------
> This SF.Net email sponsored by: Free pre-built
> ASP.NET sites including
> Data Reports, E-commerce, Portals, and Forums are
> available now.
> Download today and enter to win an XBOX or Visual
> Studio .NET.
>
http://aspnet.click-url.com/go/psa00100006ave/direct;at.asp_061203_01/01
> _______________________________________________
> Quickfix-developers mailing list
> Qui...@li...
>
https://lists.sourceforge.net/lists/listinfo/quickfix-developers


__________________________________
Do you Yahoo!?
SBC Yahoo! DSL - Now only $29.95 per month!
http://sbc.yahoo.com

Re: [Quickfix-users] Possible Checksum bug originating in FieldBase::setString()

[Oren M. <ore...@ya...>]

Yeah, also setField needs to recalculate the values
which wasn't being done.  I checked in a path + unit
test for this.

http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/quickfix/quickfix/src/C++/Field.h.diff?r1=1.6&r2=1.7
http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/quickfix/quickfix/src/C++/test/Makefile.am.diff?r1=1.3&r2=1.4
http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/quickfix/quickfix/src/C++/test/TestSuite.h.diff?r1=1.1&r2=1.2&sortby=date
http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/quickfix/quickfix/src/C++/test/FieldBaseTestCase.h
http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/quickfix/quickfix/src/C++/test/FieldBaseTestCase.cpp

--- "Brendan B. Boerner" <br...@ka...>
wrote:
> Hello,
> 
> In Field.h::void FieldBase::setString( const
> std::string& string ),
> shouldn't m_total be inited to 0 before accumulating
> it? e.g.
> 
>   void 
>   { 
>     m_string = string;
>     m_data = IntConvertor::convert(m_field) + "=" +
> string + "\001";
>     m_length = m_data.length();
>     const char* iter = m_data.c_str();
>     const char* end = iter + m_data.length();
> 
>     // tbd1234: brendan - bug?
>     m_total = 0;
>     while( iter != end )
>       m_total += *iter++;
>   }
> 
> 
> W/o this, something like:
> 
> FIX::ExecType execType;
> FIX::OrdStatus ordStatus;
> execType.setValue(FIX::ExecType_NEW);
> ordStatus.setValue(FIX::OrdStatus_NEW);
> 
> ...send ExecReport... 
> 
> would cause a checksum mismatch between executor and
> a client due to
> these two fields.
> 
> In addition to not getting the checksum errors, this
> also appears to
> have fixed another problem I saw where executor
> would repeatedly ask
> my client (and possible the client would ask the
> executor - depending
> on the state at that moment) for resends.  While
> debugging the
> checksum problem I found cases where the client, in
> attempting to
> honor the resend would throw an InvalidMessage due
> to a message gap
> in the FileStore e.g. the FileStore would have
> messages 5, 6, 7, 9,
> 10 as a "" string was being pushed onto the queue of
> messages to
> resend.
> 
> Since applying the m_total = 0 fix, I've been able
> to down executor,
> bring it up and have it resync w/the client with
> none of the problems
> I've previously seen.
> 
> Regards,
> Brendan
> 
> 
> 
>
-------------------------------------------------------
> This SF.Net email sponsored by: Free pre-built
> ASP.NET sites including
> Data Reports, E-commerce, Portals, and Forums are
> available now.
> Download today and enter to win an XBOX or Visual
> Studio .NET.
>
http://aspnet.click-url.com/go/psa00100006ave/direct;at.asp_061203_01/01
> _______________________________________________
> Quickfix-users mailing list
> Qui...@li...
> https://lists.sourceforge.net/lists/listinfo/quickfix-users

__________________________________
Do you Yahoo!?
SBC Yahoo! DSL - Now only $29.95 per month!
http://sbc.yahoo.com

[Quickfix-users] FIXML Support

[Vamsi K. <Vam...@ib...>]

Hi all
I know this question has been raised earlier. Will Quickfix come up with
the Translation tool to convert its proprietary XML form of FIX message
to "Official" FIXML message.

I don't know XSLT and I would appreciate if somebody comes up with a
sample program (XSLT) to make this translation possible. I would in turn
contribute to QuickfIX group by programming the entire message set.

I have requirement to this regard from my client. Also I would like to
whether XMLField is supported in QuickFIX.

Any help is appreciated

Vamsi

[Quickfix-users] Possible Checksum bug originating in FieldBase::setString()

[Brendan B. B. <br...@ka...>]

Hello,

In Field.h::void FieldBase::setString( const std::string& string ),
shouldn't m_total be inited to 0 before accumulating it? e.g.

  void 
  { 
    m_string = string;
    m_data = IntConvertor::convert(m_field) + "=" + string + "\001";
    m_length = m_data.length();
    const char* iter = m_data.c_str();
    const char* end = iter + m_data.length();

    // tbd1234: brendan - bug?
    m_total = 0;
    while( iter != end )
      m_total += *iter++;
  }


W/o this, something like:

FIX::ExecType execType;
FIX::OrdStatus ordStatus;
execType.setValue(FIX::ExecType_NEW);
ordStatus.setValue(FIX::OrdStatus_NEW);

...send ExecReport... 

would cause a checksum mismatch between executor and a client due to
these two fields.

In addition to not getting the checksum errors, this also appears to
have fixed another problem I saw where executor would repeatedly ask
my client (and possible the client would ask the executor - depending
on the state at that moment) for resends.  While debugging the
checksum problem I found cases where the client, in attempting to
honor the resend would throw an InvalidMessage due to a message gap
in the FileStore e.g. the FileStore would have messages 5, 6, 7, 9,
10 as a "" string was being pushed onto the queue of messages to
resend.

Since applying the m_total = 0 fix, I've been able to down executor,
bring it up and have it resync w/the client with none of the problems
I've previously seen.

Regards,
Brendan

Re: [Quickfix-users] problems compiling

[Oren M. <ore...@ya...>]

Well I see some linker warnings but no errors.  Do you
see these warning if you build a release version? 
What happens when you run the unit tests?

--- Dave <vog...@ya...> wrote:
> I was able to compile everything and get quickfix up
> and running using Visual Studio 6 and no MySQL.
> 
> Now, I'm trying to compile MySQL support into
> QuickFIX
> and it's not working.
> I changed config_windows.h so that this line is not
> commented out:
> #define HAVE_MYSQL 1
> 
> When I recompiled in Visual Studio 6 it didn't work.
> So, I upgraded to Visual Studio .NET 7 and it still
> doesn't work.
> 
> Does anyone have specific instructions for compiling
> in Visual Studio .NET 7 with support for MySQL? 
> What
> exactly should be in the VC++ Directories Include
> file
> and Library files lists?
> What should my PATH be?
> Anything else you can think of will be much
> appreciated.
> This is the output I get when trying to compile
> quickfix.dsw in Visual Studio .NET 7:
> 
> ------ Rebuild All started: Project: quickfix_lib,
> Configuration: Debug Win32 ------
> 
> Deleting intermediate files and output files for
> project 'quickfix_lib', configuration 'Debug|Win32'.
> Performing Custom Build Step
>
C:\Download\QuickFIX\quickfix-1.4.0\quickfix\src\C++\MySQLStore.h
> 1 File(s) copied
> Performing Custom Build Step
>
C:\Download\QuickFIX\quickfix-1.4.0\quickfix\src\C++\MySQLLog.h
> 1 File(s) copied
> Performing Custom Build Step
>
C:\Download\QuickFIX\quickfix-1.4.0\quickfix\src\C++\MessageStore.h
> 1 File(s) copied
> Performing Custom Build Step
>
C:\Download\QuickFIX\quickfix-1.4.0\quickfix\src\C++\Log.h
> 1 File(s) copied
> Performing Custom Build Step
>
C:\Download\QuickFIX\quickfix-1.4.0\quickfix\src\C++\FileStore.h
> 1 File(s) copied
> Performing Custom Build Step
>
C:\Download\QuickFIX\quickfix-1.4.0\quickfix\src\C++\FileLog.h
> 1 File(s) copied
> Performing Custom Build Step
>
C:\Download\QuickFIX\quickfix-1.4.0\quickfix\src\C++\ThreadedSocketInitiator.h
> 1 File(s) copied
> Performing Custom Build Step
>
C:\Download\QuickFIX\quickfix-1.4.0\quickfix\src\C++\ThreadedSocketConnection.h
> 1 File(s) copied
> Performing Custom Build Step
>
C:\Download\QuickFIX\quickfix-1.4.0\quickfix\src\C++\ThreadedSocketAcceptor.h
> 1 File(s) copied
> Performing Custom Build Step
>
C:\Download\QuickFIX\quickfix-1.4.0\quickfix\src\C++\SocketServer.h
> 1 File(s) copied
> Performing Custom Build Step
>
C:\Download\QuickFIX\quickfix-1.4.0\quickfix\src\C++\SocketMonitor.h
> 1 File(s) copied
> Performing Custom Build Step
>
C:\Download\QuickFIX\quickfix-1.4.0\quickfix\src\C++\SocketInitiator.h
> 1 File(s) copied
> Performing Custom Build Step
>
C:\Download\QuickFIX\quickfix-1.4.0\quickfix\src\C++\SocketConnector.h
> 1 File(s) copied
> Performing Custom Build Step
>
C:\Download\QuickFIX\quickfix-1.4.0\quickfix\src\C++\SocketConnection.h
> 1 File(s) copied
> Performing Custom Build Step
>
C:\Download\QuickFIX\quickfix-1.4.0\quickfix\src\C++\SocketAcceptor.h
> 1 File(s) copied
> Performing Custom Build Step
>
C:\Download\QuickFIX\quickfix-1.4.0\quickfix\src\C++\MessageSorters.h
> 1 File(s) copied
> Performing Custom Build Step
>
C:\Download\QuickFIX\quickfix-1.4.0\quickfix\src\C++\Messages.h
> 1 File(s) copied
> Performing Custom Build Step
>
C:\Download\QuickFIX\quickfix-1.4.0\quickfix\src\C++\MessageCracker.h
> 1 File(s) copied
> Performing Custom Build Step
>
C:\Download\QuickFIX\quickfix-1.4.0\quickfix\src\C++\Message.h
> 1 File(s) copied
> Performing Custom Build Step
>
C:\Download\QuickFIX\quickfix-1.4.0\quickfix\src\C++\Group.h
> 1 File(s) copied
> Performing Custom Build Step
>
C:\Download\QuickFIX\quickfix-1.4.0\quickfix\src\C++\FIX43_Messages.h
> 1 File(s) copied
> Performing Custom Build Step
>
C:\Download\QuickFIX\quickfix-1.4.0\quickfix\src\C++\FIX43_MessageCracker.h
> 1 File(s) copied
> Performing Custom Build Step
>
C:\Download\QuickFIX\quickfix-1.4.0\quickfix\src\C++\FIX42_Messages.h
> 1 File(s) copied
> Performing Custom Build Step
>
C:\Download\QuickFIX\quickfix-1.4.0\quickfix\src\C++\FIX42_MessageCracker.h
> 1 File(s) copied
> Performing Custom Build Step
>
C:\Download\QuickFIX\quickfix-1.4.0\quickfix\src\C++\FIX41_Messages.h
> 1 File(s) copied
> Performing Custom Build Step
>
C:\Download\QuickFIX\quickfix-1.4.0\quickfix\src\C++\FIX41_MessageCracker.h
> 1 File(s) copied
> Performing Custom Build Step
>
C:\Download\QuickFIX\quickfix-1.4.0\quickfix\src\C++\FIX40_Messages.h
> 1 File(s) copied
> Performing Custom Build Step
>
C:\Download\QuickFIX\quickfix-1.4.0\quickfix\src\C++\FIX40_MessageCracker.h
> 1 File(s) copied
> Performing Custom Build Step
>
C:\Download\QuickFIX\quickfix-1.4.0\quickfix\src\C++\DataDictionary.h
> 1 File(s) copied
> Performing Custom Build Step
>
C:\Download\QuickFIX\quickfix-1.4.0\quickfix\src\C++\Values.h
> 1 File(s) copied
> Performing Custom Build Step
>
C:\Download\QuickFIX\quickfix-1.4.0\quickfix\src\C++\FieldTypes.h
> 1 File(s) copied
> Performing Custom Build Step
>
C:\Download\QuickFIX\quickfix-1.4.0\quickfix\src\C++\Fields.h
> 1 File(s) copied
> Performing Custom Build Step
>
C:\Download\QuickFIX\quickfix-1.4.0\quickfix\src\C++\FieldNumbers.h
> 1 File(s) copied
> Performing Custom Build Step
>
C:\Download\QuickFIX\quickfix-1.4.0\quickfix\src\C++\FieldMap.h
> 1 File(s) copied
> Performing Custom Build Step
>
C:\Download\QuickFIX\quickfix-1.4.0\quickfix\src\C++\FieldConvertors.h
> 1 File(s) copied
> Performing Custom Build Step
>
C:\Download\QuickFIX\quickfix-1.4.0\quickfix\src\C++\Field.h
> 1 File(s) copied
> Performing Custom Build Step
>
C:\Download\QuickFIX\quickfix-1.4.0\quickfix\src\C++\DeprecatedValues.h
> 1 File(s) copied
> Performing Custom Build Step
>
C:\Download\QuickFIX\quickfix-1.4.0\quickfix\src\C++\DeprecatedFields.h
> 1 File(s) copied
> Performing Custom Build Step
>
C:\Download\QuickFIX\quickfix-1.4.0\quickfix\src\C++\DeprecatedFieldNumbers.h
> 1 File(s) copied
> Performing Custom Build Step
>
C:\Download\QuickFIX\quickfix-1.4.0\quickfix\src\C++\Utility.h
> 1 File(s) copied
> Performing Custom Build Step
>
C:\Download\QuickFIX\quickfix-1.4.0\quickfix\src\C++\strptime.h
> 1 File(s) copied
> Performing Custom Build Step
>
C:\Download\QuickFIX\quickfix-1.4.0\quickfix\src\C++\Settings.h
> 1 File(s) copied
> Performing Custom Build Step
>
C:\Download\QuickFIX\quickfix-1.4.0\quickfix\src\C++\SessionState.h
> 1 File(s) copied
> Performing Custom Build Step
>
C:\Download\QuickFIX\quickfix-1.4.0\quickfix\src\C++\SessionSettings.h
> 1 File(s) copied
> Performing Custom Build Step
>
C:\Download\QuickFIX\quickfix-1.4.0\quickfix\src\C++\SessionID.h
> 1 File(s) copied
> Performing Custom Build Step
>
C:\Download\QuickFIX\quickfix-1.4.0\quickfix\src\C++\SessionFactory.h
> 1 File(s) copied
> Performing Custom Build Step
>
C:\Download\QuickFIX\quickfix-1.4.0\quickfix\src\C++\Session.h
> 1 File(s) copied
> Performing Custom Build Step
>
C:\Download\QuickFIX\quickfix-1.4.0\quickfix\src\C++\Queue.h
> 1 File(s) copied
> Performing Custom Build Step
>
C:\Download\QuickFIX\quickfix-1.4.0\quickfix\src\C++\Parser.h
> 1 File(s) copied
> Performing Custom Build Step
>
C:\Download\QuickFIX\quickfix-1.4.0\quickfix\src\C++\Mutex.h
> 1 File(s) copied
> Performing Custom Build Step
>
C:\Download\QuickFIX\quickfix-1.4.0\quickfix\src\C++\MSXML_DOMDocument.h
> 1 File(s) copied
> Performing Custom Build Step
>
C:\Download\QuickFIX\quickfix-1.4.0\quickfix\src\C++\Initiator.h
> 1 File(s) copied
> Performing Custom Build Step
>
C:\Download\QuickFIX\quickfix-1.4.0\quickfix\src\C++\index.h
> 1 File(s) copied
> Performing Custom Build Step
>
C:\Download\QuickFIX\quickfix-1.4.0\quickfix\src\C++\FlexLexer.h
> 1 File(s) copied
> Performing Custom Build Step
>
C:\Download\QuickFIX\quickfix-1.4.0\quickfix\src\C++\Exceptions.h
> 1 File(s) copied
> Performing Custom Build Step
>
C:\Download\QuickFIX\quickfix-1.4.0\quickfix\src\C++\Event.h
> 1 File(s) copied
> Performing Custom Build Step
>
C:\Download\QuickFIX\quickfix-1.4.0\quickfix\src\C++\DOMDocument.h
> 
=== message truncated ===

__________________________________
Do you Yahoo!?
SBC Yahoo! DSL - Now only $29.95 per month!
http://sbc.yahoo.com

[Quickfix-users] problems compiling

[Dave <vog...@ya...>]

I was able to compile everything and get quickfix up
and running using Visual Studio 6 and no MySQL.

Now, I'm trying to compile MySQL support into QuickFIX
and it's not working.
I changed config_windows.h so that this line is not
commented out:
#define HAVE_MYSQL 1

When I recompiled in Visual Studio 6 it didn't work.
So, I upgraded to Visual Studio .NET 7 and it still
doesn't work.

Does anyone have specific instructions for compiling
in Visual Studio .NET 7 with support for MySQL?  What
exactly should be in the VC++ Directories Include file
and Library files lists?
What should my PATH be?
Anything else you can think of will be much
appreciated.
This is the output I get when trying to compile
quickfix.dsw in Visual Studio .NET 7:

------ Rebuild All started: Project: quickfix_lib,
Configuration: Debug Win32 ------

Deleting intermediate files and output files for
project 'quickfix_lib', configuration 'Debug|Win32'.
Performing Custom Build Step
C:\Download\QuickFIX\quickfix-1.4.0\quickfix\src\C++\MySQLStore.h
1 File(s) copied
Performing Custom Build Step
C:\Download\QuickFIX\quickfix-1.4.0\quickfix\src\C++\MySQLLog.h
1 File(s) copied
Performing Custom Build Step
C:\Download\QuickFIX\quickfix-1.4.0\quickfix\src\C++\MessageStore.h
1 File(s) copied
Performing Custom Build Step
C:\Download\QuickFIX\quickfix-1.4.0\quickfix\src\C++\Log.h
1 File(s) copied
Performing Custom Build Step
C:\Download\QuickFIX\quickfix-1.4.0\quickfix\src\C++\FileStore.h
1 File(s) copied
Performing Custom Build Step
C:\Download\QuickFIX\quickfix-1.4.0\quickfix\src\C++\FileLog.h
1 File(s) copied
Performing Custom Build Step
C:\Download\QuickFIX\quickfix-1.4.0\quickfix\src\C++\ThreadedSocketInitiator.h
1 File(s) copied
Performing Custom Build Step
C:\Download\QuickFIX\quickfix-1.4.0\quickfix\src\C++\ThreadedSocketConnection.h
1 File(s) copied
Performing Custom Build Step
C:\Download\QuickFIX\quickfix-1.4.0\quickfix\src\C++\ThreadedSocketAcceptor.h
1 File(s) copied
Performing Custom Build Step
C:\Download\QuickFIX\quickfix-1.4.0\quickfix\src\C++\SocketServer.h
1 File(s) copied
Performing Custom Build Step
C:\Download\QuickFIX\quickfix-1.4.0\quickfix\src\C++\SocketMonitor.h
1 File(s) copied
Performing Custom Build Step
C:\Download\QuickFIX\quickfix-1.4.0\quickfix\src\C++\SocketInitiator.h
1 File(s) copied
Performing Custom Build Step
C:\Download\QuickFIX\quickfix-1.4.0\quickfix\src\C++\SocketConnector.h
1 File(s) copied
Performing Custom Build Step
C:\Download\QuickFIX\quickfix-1.4.0\quickfix\src\C++\SocketConnection.h
1 File(s) copied
Performing Custom Build Step
C:\Download\QuickFIX\quickfix-1.4.0\quickfix\src\C++\SocketAcceptor.h
1 File(s) copied
Performing Custom Build Step
C:\Download\QuickFIX\quickfix-1.4.0\quickfix\src\C++\MessageSorters.h
1 File(s) copied
Performing Custom Build Step
C:\Download\QuickFIX\quickfix-1.4.0\quickfix\src\C++\Messages.h
1 File(s) copied
Performing Custom Build Step
C:\Download\QuickFIX\quickfix-1.4.0\quickfix\src\C++\MessageCracker.h
1 File(s) copied
Performing Custom Build Step
C:\Download\QuickFIX\quickfix-1.4.0\quickfix\src\C++\Message.h
1 File(s) copied
Performing Custom Build Step
C:\Download\QuickFIX\quickfix-1.4.0\quickfix\src\C++\Group.h
1 File(s) copied
Performing Custom Build Step
C:\Download\QuickFIX\quickfix-1.4.0\quickfix\src\C++\FIX43_Messages.h
1 File(s) copied
Performing Custom Build Step
C:\Download\QuickFIX\quickfix-1.4.0\quickfix\src\C++\FIX43_MessageCracker.h
1 File(s) copied
Performing Custom Build Step
C:\Download\QuickFIX\quickfix-1.4.0\quickfix\src\C++\FIX42_Messages.h
1 File(s) copied
Performing Custom Build Step
C:\Download\QuickFIX\quickfix-1.4.0\quickfix\src\C++\FIX42_MessageCracker.h
1 File(s) copied
Performing Custom Build Step
C:\Download\QuickFIX\quickfix-1.4.0\quickfix\src\C++\FIX41_Messages.h
1 File(s) copied
Performing Custom Build Step
C:\Download\QuickFIX\quickfix-1.4.0\quickfix\src\C++\FIX41_MessageCracker.h
1 File(s) copied
Performing Custom Build Step
C:\Download\QuickFIX\quickfix-1.4.0\quickfix\src\C++\FIX40_Messages.h
1 File(s) copied
Performing Custom Build Step
C:\Download\QuickFIX\quickfix-1.4.0\quickfix\src\C++\FIX40_MessageCracker.h
1 File(s) copied
Performing Custom Build Step
C:\Download\QuickFIX\quickfix-1.4.0\quickfix\src\C++\DataDictionary.h
1 File(s) copied
Performing Custom Build Step
C:\Download\QuickFIX\quickfix-1.4.0\quickfix\src\C++\Values.h
1 File(s) copied
Performing Custom Build Step
C:\Download\QuickFIX\quickfix-1.4.0\quickfix\src\C++\FieldTypes.h
1 File(s) copied
Performing Custom Build Step
C:\Download\QuickFIX\quickfix-1.4.0\quickfix\src\C++\Fields.h
1 File(s) copied
Performing Custom Build Step
C:\Download\QuickFIX\quickfix-1.4.0\quickfix\src\C++\FieldNumbers.h
1 File(s) copied
Performing Custom Build Step
C:\Download\QuickFIX\quickfix-1.4.0\quickfix\src\C++\FieldMap.h
1 File(s) copied
Performing Custom Build Step
C:\Download\QuickFIX\quickfix-1.4.0\quickfix\src\C++\FieldConvertors.h
1 File(s) copied
Performing Custom Build Step
C:\Download\QuickFIX\quickfix-1.4.0\quickfix\src\C++\Field.h
1 File(s) copied
Performing Custom Build Step
C:\Download\QuickFIX\quickfix-1.4.0\quickfix\src\C++\DeprecatedValues.h
1 File(s) copied
Performing Custom Build Step
C:\Download\QuickFIX\quickfix-1.4.0\quickfix\src\C++\DeprecatedFields.h
1 File(s) copied
Performing Custom Build Step
C:\Download\QuickFIX\quickfix-1.4.0\quickfix\src\C++\DeprecatedFieldNumbers.h
1 File(s) copied
Performing Custom Build Step
C:\Download\QuickFIX\quickfix-1.4.0\quickfix\src\C++\Utility.h
1 File(s) copied
Performing Custom Build Step
C:\Download\QuickFIX\quickfix-1.4.0\quickfix\src\C++\strptime.h
1 File(s) copied
Performing Custom Build Step
C:\Download\QuickFIX\quickfix-1.4.0\quickfix\src\C++\Settings.h
1 File(s) copied
Performing Custom Build Step
C:\Download\QuickFIX\quickfix-1.4.0\quickfix\src\C++\SessionState.h
1 File(s) copied
Performing Custom Build Step
C:\Download\QuickFIX\quickfix-1.4.0\quickfix\src\C++\SessionSettings.h
1 File(s) copied
Performing Custom Build Step
C:\Download\QuickFIX\quickfix-1.4.0\quickfix\src\C++\SessionID.h
1 File(s) copied
Performing Custom Build Step
C:\Download\QuickFIX\quickfix-1.4.0\quickfix\src\C++\SessionFactory.h
1 File(s) copied
Performing Custom Build Step
C:\Download\QuickFIX\quickfix-1.4.0\quickfix\src\C++\Session.h
1 File(s) copied
Performing Custom Build Step
C:\Download\QuickFIX\quickfix-1.4.0\quickfix\src\C++\Queue.h
1 File(s) copied
Performing Custom Build Step
C:\Download\QuickFIX\quickfix-1.4.0\quickfix\src\C++\Parser.h
1 File(s) copied
Performing Custom Build Step
C:\Download\QuickFIX\quickfix-1.4.0\quickfix\src\C++\Mutex.h
1 File(s) copied
Performing Custom Build Step
C:\Download\QuickFIX\quickfix-1.4.0\quickfix\src\C++\MSXML_DOMDocument.h
1 File(s) copied
Performing Custom Build Step
C:\Download\QuickFIX\quickfix-1.4.0\quickfix\src\C++\Initiator.h
1 File(s) copied
Performing Custom Build Step
C:\Download\QuickFIX\quickfix-1.4.0\quickfix\src\C++\index.h
1 File(s) copied
Performing Custom Build Step
C:\Download\QuickFIX\quickfix-1.4.0\quickfix\src\C++\FlexLexer.h
1 File(s) copied
Performing Custom Build Step
C:\Download\QuickFIX\quickfix-1.4.0\quickfix\src\C++\Exceptions.h
1 File(s) copied
Performing Custom Build Step
C:\Download\QuickFIX\quickfix-1.4.0\quickfix\src\C++\Event.h
1 File(s) copied
Performing Custom Build Step
C:\Download\QuickFIX\quickfix-1.4.0\quickfix\src\C++\DOMDocument.h
1 File(s) copied
Performing Custom Build Step
C:\Download\QuickFIX\quickfix-1.4.0\quickfix\src\C++\Dictionary.h
1 File(s) copied
Performing Custom Build Step
C:\Download\QuickFIX\quickfix-1.4.0\quickfix\src\C++\ConfigLexer.h
1 File(s) copied
Performing Custom Build Step
C:\Download\QuickFIX\quickfix-1.4.0\quickfix\src\C++\Application.h
1 File(s) copied
Performing Custom Build Step
C:\Download\QuickFIX\quickfix-1.4.0\quickfix\src\C++\Acceptor.h
1 File(s) copied
Compiling...
MySQLStore.cpp
MySQLLog.cpp
MessageStore.cpp
Log.cpp
FileStore.cpp
FileLog.cpp
ThreadedSocketInitiator.cpp
ThreadedSocketConnection.cpp
ThreadedSocketAcceptor.cpp
SocketServer.cpp
SocketMonitor.cpp
SocketInitiator.cpp
SocketConnector.cpp
SocketConnection.cpp
SocketAcceptor.cpp
MessageSorters.cpp
Message.cpp
Group.cpp
DataDictionary.cpp
FieldTypes.cpp
Utility.cpp
strptime.c
stdafx.cpp
Settings.cpp
SessionSettings.cpp
SessionFactory.cpp
Session.cpp
Parser.cpp
MSXML_DOMDocument.cpp
Initiator.cpp
Dictionary.cpp
ConfigLexer.cpp
Acceptor.cpp
Creating library...

Build log was saved at
"file://c:\Download\QuickFIX\quickfix-1.4.0\quickfix\Debug\BuildLog.htm"
quickfix_lib - 0 error(s), 0 warning(s)


------ Rebuild All started: Project: at_server,
Configuration: Debug Win32 ------

Deleting intermediate files and output files for
project 'at_server', configuration 'Debug|Win32'.
Compiling...
getopt.c
at_server.cpp
Linking...
quickfix_debug.lib(Acceptor.obj) : warning LNK4204:
'c:\Download\QuickFIX\quickfix-1.4.0\quickfix\Debug\vc70.pdb'
is missing debugging information for referencing
module; linking object as if no debug info
quickfix_debug.lib(ConfigLexer.obj) : warning LNK4204:
'c:\Download\QuickFIX\quickfix-1.4.0\quickfix\Debug\vc70.pdb'
is missing debugging information for referencing
module; linking object as if no debug info
quickfix_debug.lib(Dictionary.obj) : warning LNK4204:
'c:\Download\QuickFIX\quickfix-1.4.0\quickfix\Debug\vc70.pdb'
is missing debugging information for referencing
module; linking object as if no debug info
quickfix_debug.lib(Initiator.obj) : warning LNK4204:
'c:\Download\QuickFIX\quickfix-1.4.0\quickfix\Debug\vc70.pdb'
is missing debugging information for referencing
module; linking object as if no debug info
quickfix_debug.lib(MSXML_DOMDocument.obj) : warning
LNK4204:
'c:\Download\QuickFIX\quickfix-1.4.0\quickfix\Debug\vc70.pdb'
is missing debugging information for referencing
module; linking object as if no debug info
quickfix_debug.lib(Parser.obj) : warning LNK4204:
'c:\Download\QuickFIX\quickfix-1.4.0\quickfix\Debug\vc70.pdb'
is missing debugging information for referencing
module; linking object as if no debug info
quickfix_debug.lib(Session.obj) : warning LNK4204:
'c:\Download\QuickFIX\quickfix-1.4.0\quickfix\Debug\vc70.pdb'
is missing debugging information for referencing
module; linking object as if no debug info
quickfix_debug.lib(SessionFactory.obj) : warning
LNK4204:
'c:\Download\QuickFIX\quickfix-1.4.0\quickfix\Debug\vc70.pdb'
is missing debugging information for referencing
module; linking object as if no debug info
quickfix_debug.lib(SessionSettings.obj) : warning
LNK4204:
'c:\Download\QuickFIX\quickfix-1.4.0\quickfix\Debug\vc70.pdb'
is missing debugging information for referencing
module; linking object as if no debug info
quickfix_debug.lib(Settings.obj) : warning LNK4204:
'c:\Download\QuickFIX\quickfix-1.4.0\quickfix\Debug\vc70.pdb'
is missing debugging information for referencing
module; linking object as if no debug info
quickfix_debug.lib(strptime.obj) : warning LNK4204:
'c:\Download\QuickFIX\quickfix-1.4.0\quickfix\Debug\vc70.pdb'
is missing debugging information for referencing
module; linking object as if no debug info
quickfix_debug.lib(Utility.obj) : warning LNK4204:
'c:\Download\QuickFIX\quickfix-1.4.0\quickfix\Debug\vc70.pdb'
is missing debugging information for referencing
module; linking object as if no debug info
quickfix_debug.lib(DataDictionary.obj) : warning
LNK4204:
'c:\Download\QuickFIX\quickfix-1.4.0\quickfix\Debug\vc70.pdb'
is missing debugging information for referencing
module; linking object as if no debug info
quickfix_debug.lib(Message.obj) : warning LNK4204:
'c:\Download\QuickFIX\quickfix-1.4.0\quickfix\Debug\vc70.pdb'
is missing debugging information for referencing
module; linking object as if no debug info
quickfix_debug.lib(MessageSorters.obj) : warning
LNK4204:
'c:\Download\QuickFIX\quickfix-1.4.0\quickfix\Debug\vc70.pdb'
is missing debugging information for referencing
module; linking object as if no debug info
quickfix_debug.lib(SocketAcceptor.obj) : warning
LNK4204:
'c:\Download\QuickFIX\quickfix-1.4.0\quickfix\Debug\vc70.pdb'
is missing debugging information for referencing
module; linking object as if no debug info
quickfix_debug.lib(SocketConnection.obj) : warning
LNK4204:
'c:\Download\QuickFIX\quickfix-1.4.0\quickfix\Debug\vc70.pdb'
is missing debugging information for referencing
module; linking object as if no debug info
quickfix_debug.lib(SocketMonitor.obj) : warning
LNK4204:
'c:\Download\QuickFIX\quickfix-1.4.0\quickfix\Debug\vc70.pdb'
is missing debugging information for referencing
module; linking object as if no debug info
quickfix_debug.lib(SocketServer.obj) : warning
LNK4204:
'c:\Download\QuickFIX\quickfix-1.4.0\quickfix\Debug\vc70.pdb'
is missing debugging information for referencing
module; linking object as if no debug info
quickfix_debug.lib(ThreadedSocketAcceptor.obj) :
warning LNK4204:
'c:\Download\QuickFIX\quickfix-1.4.0\quickfix\Debug\vc70.pdb'
is missing debugging information for referencing
module; linking object as if no debug info
quickfix_debug.lib(ThreadedSocketConnection.obj) :
warning LNK4204:
'c:\Download\QuickFIX\quickfix-1.4.0\quickfix\Debug\vc70.pdb'
is missing debugging information for referencing
module; linking object as if no debug info
quickfix_debug.lib(FileStore.obj) : warning LNK4204:
'c:\Download\QuickFIX\quickfix-1.4.0\quickfix\Debug\vc70.pdb'
is missing debugging information for referencing
module; linking object as if no debug info
quickfix_debug.lib(MessageStore.obj) : warning
LNK4204:
'c:\Download\QuickFIX\quickfix-1.4.0\quickfix\Debug\vc70.pdb'
is missing debugging information for referencing
module; linking object as if no debug info

Build log was saved at
"file://c:\Download\QuickFIX\quickfix-1.4.0\quickfix\Debug\BuildLog.htm"
at_server - 0 error(s), 23 warning(s)


------ Rebuild All started: Project: atrun,
Configuration: Debug Win32 ------

Deleting intermediate files and output files for
project 'atrun', configuration 'Debug|Win32'.
Compiling...
ProcessTestCase.cpp
Process.cpp
main.cpp
getopt.c
Linking...

Build log was saved at
"file://c:\Download\QuickFIX\quickfix-1.4.0\quickfix\test\atrun\Debug\BuildLog.htm"
atrun - 0 error(s), 0 warning(s)


------ Rebuild All started: Project: pt,
Configuration: Debug Win32 ------

Deleting intermediate files and output files for
project 'pt', configuration 'Debug|Win32'.
Compiling...
pt.cpp
getopt.c
Linking...
quickfix_debug.lib(ConfigLexer.obj) : warning LNK4204:
'c:\Download\QuickFIX\quickfix-1.4.0\quickfix\Debug\vc70.pdb'
is missing debugging information for referencing
module; linking object as if no debug info
quickfix_debug.lib(Dictionary.obj) : warning LNK4204:
'c:\Download\QuickFIX\quickfix-1.4.0\quickfix\Debug\vc70.pdb'
is missing debugging information for referencing
module; linking object as if no debug info
quickfix_debug.lib(MSXML_DOMDocument.obj) : warning
LNK4204:
'c:\Download\QuickFIX\quickfix-1.4.0\quickfix\Debug\vc70.pdb'
is missing debugging information for referencing
module; linking object as if no debug info
quickfix_debug.lib(SessionSettings.obj) : warning
LNK4204:
'c:\Download\QuickFIX\quickfix-1.4.0\quickfix\Debug\vc70.pdb'
is missing debugging information for referencing
module; linking object as if no debug info
quickfix_debug.lib(Settings.obj) : warning LNK4204:
'c:\Download\QuickFIX\quickfix-1.4.0\quickfix\Debug\vc70.pdb'
is missing debugging information for referencing
module; linking object as if no debug info
quickfix_debug.lib(strptime.obj) : warning LNK4204:
'c:\Download\QuickFIX\quickfix-1.4.0\quickfix\Debug\vc70.pdb'
is missing debugging information for referencing
module; linking object as if no debug info
quickfix_debug.lib(Utility.obj) : warning LNK4204:
'c:\Download\QuickFIX\quickfix-1.4.0\quickfix\Debug\vc70.pdb'
is missing debugging information for referencing
module; linking object as if no debug info
quickfix_debug.lib(DataDictionary.obj) : warning
LNK4204:
'c:\Download\QuickFIX\quickfix-1.4.0\quickfix\Debug\vc70.pdb'
is missing debugging information for referencing
module; linking object as if no debug info
quickfix_debug.lib(Message.obj) : warning LNK4204:
'c:\Download\QuickFIX\quickfix-1.4.0\quickfix\Debug\vc70.pdb'
is missing debugging information for referencing
module; linking object as if no debug info
quickfix_debug.lib(MessageSorters.obj) : warning
LNK4204:
'c:\Download\QuickFIX\quickfix-1.4.0\quickfix\Debug\vc70.pdb'
is missing debugging information for referencing
module; linking object as if no debug info
quickfix_debug.lib(FileStore.obj) : warning LNK4204:
'c:\Download\QuickFIX\quickfix-1.4.0\quickfix\Debug\vc70.pdb'
is missing debugging information for referencing
module; linking object as if no debug info
quickfix_debug.lib(MessageStore.obj) : warning
LNK4204:
'c:\Download\QuickFIX\quickfix-1.4.0\quickfix\Debug\vc70.pdb'
is missing debugging information for referencing
module; linking object as if no debug info

Build log was saved at
"file://c:\Download\QuickFIX\quickfix-1.4.0\quickfix\Debug\BuildLog.htm"
pt - 0 error(s), 12 warning(s)


------ Rebuild All started: Project: ut,
Configuration: Debug Win32 ------

Deleting intermediate files and output files for
project 'ut', configuration 'Debug|Win32'.
Compiling...
UtcTimeStampTestCase.cpp
UtcTimeOnlyTestCase.cpp
ut.cpp
SocketUtilitiesTestCase.cpp
SocketServerTestCase.cpp
SocketConnectorTestCase.cpp
SettingsTestCase.cpp
SessionTestCase.cpp
SessionSettingsTestCase.cpp
SessionIDTestCase.cpp
ParserTestCase.cpp
MySQLStoreTestCase.cpp
MessageStoreTestCase.cpp
MessagesTestCase.cpp
getopt.c
FileStoreTestCase.cpp
FileStoreFactoryTestCase.cpp
FieldConvertorsTestCase.cpp
DictionaryTestCase.cpp
DataDictionaryTestCase.cpp
AcceptorTestCase.cpp
Linking...
quickfix_debug.lib(Acceptor.obj) : warning LNK4204:
'c:\Download\QuickFIX\quickfix-1.4.0\quickfix\Debug\vc70.pdb'
is missing debugging information for referencing
module; linking object as if no debug info
quickfix_debug.lib(ConfigLexer.obj) : warning LNK4204:
'c:\Download\QuickFIX\quickfix-1.4.0\quickfix\Debug\vc70.pdb'
is missing debugging information for referencing
module; linking object as if no debug info
quickfix_debug.lib(Dictionary.obj) : warning LNK4204:
'c:\Download\QuickFIX\quickfix-1.4.0\quickfix\Debug\vc70.pdb'
is missing debugging information for referencing
module; linking object as if no debug info
quickfix_debug.lib(MSXML_DOMDocument.obj) : warning
LNK4204:
'c:\Download\QuickFIX\quickfix-1.4.0\quickfix\Debug\vc70.pdb'
is missing debugging information for referencing
module; linking object as if no debug info
quickfix_debug.lib(Parser.obj) : warning LNK4204:
'c:\Download\QuickFIX\quickfix-1.4.0\quickfix\Debug\vc70.pdb'
is missing debugging information for referencing
module; linking object as if no debug info
quickfix_debug.lib(Session.obj) : warning LNK4204:
'c:\Download\QuickFIX\quickfix-1.4.0\quickfix\Debug\vc70.pdb'
is missing debugging information for referencing
module; linking object as if no debug info
quickfix_debug.lib(SessionFactory.obj) : warning
LNK4204:
'c:\Download\QuickFIX\quickfix-1.4.0\quickfix\Debug\vc70.pdb'
is missing debugging information for referencing
module; linking object as if no debug info
quickfix_debug.lib(SessionSettings.obj) : warning
LNK4204:
'c:\Download\QuickFIX\quickfix-1.4.0\quickfix\Debug\vc70.pdb'
is missing debugging information for referencing
module; linking object as if no debug info
quickfix_debug.lib(Settings.obj) : warning LNK4204:
'c:\Download\QuickFIX\quickfix-1.4.0\quickfix\Debug\vc70.pdb'
is missing debugging information for referencing
module; linking object as if no debug info
quickfix_debug.lib(strptime.obj) : warning LNK4204:
'c:\Download\QuickFIX\quickfix-1.4.0\quickfix\Debug\vc70.pdb'
is missing debugging information for referencing
module; linking object as if no debug info
quickfix_debug.lib(Utility.obj) : warning LNK4204:
'c:\Download\QuickFIX\quickfix-1.4.0\quickfix\Debug\vc70.pdb'
is missing debugging information for referencing
module; linking object as if no debug info
quickfix_debug.lib(DataDictionary.obj) : warning
LNK4204:
'c:\Download\QuickFIX\quickfix-1.4.0\quickfix\Debug\vc70.pdb'
is missing debugging information for referencing
module; linking object as if no debug info
quickfix_debug.lib(Message.obj) : warning LNK4204:
'c:\Download\QuickFIX\quickfix-1.4.0\quickfix\Debug\vc70.pdb'
is missing debugging information for referencing
module; linking object as if no debug info
quickfix_debug.lib(MessageSorters.obj) : warning
LNK4204:
'c:\Download\QuickFIX\quickfix-1.4.0\quickfix\Debug\vc70.pdb'
is missing debugging information for referencing
module; linking object as if no debug info
quickfix_debug.lib(SocketConnector.obj) : warning
LNK4204:
'c:\Download\QuickFIX\quickfix-1.4.0\quickfix\Debug\vc70.pdb'
is missing debugging information for referencing
module; linking object as if no debug info
quickfix_debug.lib(SocketMonitor.obj) : warning
LNK4204:
'c:\Download\QuickFIX\quickfix-1.4.0\quickfix\Debug\vc70.pdb'
is missing debugging information for referencing
module; linking object as if no debug info
quickfix_debug.lib(SocketServer.obj) : warning
LNK4204:
'c:\Download\QuickFIX\quickfix-1.4.0\quickfix\Debug\vc70.pdb'
is missing debugging information for referencing
module; linking object as if no debug info
quickfix_debug.lib(FileStore.obj) : warning LNK4204:
'c:\Download\QuickFIX\quickfix-1.4.0\quickfix\Debug\vc70.pdb'
is missing debugging information for referencing
module; linking object as if no debug info
quickfix_debug.lib(MessageStore.obj) : warning
LNK4204:
'c:\Download\QuickFIX\quickfix-1.4.0\quickfix\Debug\vc70.pdb'
is missing debugging information for referencing
module; linking object as if no debug info
quickfix_debug.lib(MySQLStore.obj) : warning LNK4204:
'c:\Download\QuickFIX\quickfix-1.4.0\quickfix\Debug\vc70.pdb'
is missing debugging information for referencing
module; linking object as if no debug info

Build log was saved at
"file://c:\Download\QuickFIX\quickfix-1.4.0\quickfix\Debug\BuildLog.htm"
ut - 0 error(s), 20 warning(s)


---------------------- Done ----------------------

    Rebuild All: 5 succeeded, 0 failed, 0 skipped

[Quickfix-users] libMySQL.lib LINK : fatal error LNK1104: cannot open file "libMySQL.lib"

[Dave <vog...@ya...>]

I am attempting to compile with MySQL on.  I'm using
Windows 2000 Pro. and VS6 SP5.  I get the following
error:
libMySQL.lib   LINK : fatal error LNK1104:  cannot
open file "libMySQL.lib"
Any ideas?
I put C:\MYSQL\LIB\DEBUG at the top of my directories
list in VisualStudio.

[Quickfix-users] ordermatch example; incorrectly parsed DataDictionary causes crash

[Brendan B. B. <br...@ka...>]

Hello,

From "quickfix-1.5.0\doc\html\examples.html":

"The applications provided are ordermatch which is a c++ server that
will match and execute limit orders."

For some reason I introduced myself to QF using tradeclient running
against ordermatch before trying tradeclient running against executor.

I was quite perplexed as to why orders I was sending to ordermatch
were being rejected until I realized that ordermatch didn't override
FIX::MessageCracker::onMessage( const NewOrderSingle&, const
FIX::SessionID& ) as does executor.

So if Executor simply fills every limit order that it receives, what
is ordermatch intended to do?

Also, is it a known problem that if specifying a DataDictionary which
contains something in the path which the parser considers a delimeter
that there's a crash in DataDictionary::readFromURL()?

Using something like
DataDictionary=c:\Projects\c++\quickfix-1.5.0\spec\FIX41.xml will
result in a path of "c:\Projects\c" which results in a reference to a
NULL pFixNode in readFromURL().

Regards,
Brendan

Re: [Quickfix-users] Incorrect time with ScreenLogFactory

[Oren M. <ore...@ya...>]

Great.  I'll check it in.

--- "Van Gelder Eddy (KAOB 41)"
<edd...@cr...> wrote:
> Hi Oren,
> 
> I found out that the problem I had with the
> incorrect time around the EOD is caused by Log.h
> 
> in the Screenlog class m_time.setCurrent() is
> missing for onOutgoing and onEvent.
> 
> Best Regards,
> 
> Eddy
> 
> 
> 
>
-------------------------------------------------------
> This SF.Net email is sponsored by: INetU
> Attention Web Developers & Consultants: Become An
> INetU Hosting Partner.
> Refer Dedicated Servers. We Manage Them. You Get 10%
> Monthly Commission!
> INetU Dedicated Managed Hosting
> http://www.inetu.net/partner/index.php
> _______________________________________________
> Quickfix-users mailing list
> Qui...@li...
> https://lists.sourceforge.net/lists/listinfo/quickfix-users

__________________________________
Do you Yahoo!?
SBC Yahoo! DSL - Now only $29.95 per month!
http://sbc.yahoo.com

[Quickfix-users] Incorrect time with ScreenLogFactory

[Van G. E. (K. 41) <edd...@cr...>]

Hi Oren,

I found out that the problem I had with the incorrect time around the EOD is caused by Log.h

in the Screenlog class m_time.setCurrent() is missing for onOutgoing and onEvent.

Best Regards,

Eddy

RE: [Quickfix-users] QuickFIX and SLK RediFIX?

[Chuck H. <zzc...@xc...>]

Hi Brendan,

I've been using QuickFix with RediFIX successfully (we've been through =
FOC certification tests, and are now doing live pre-production tests).

The only issue we ran into was that QuickFix can't send logout messages, =
but it wasn't a show-stopper.

Some details:

QuickFix 1.4/1.5 Java Interface
Platforms: W2k and Solaris
Target: FOC's RediFIX FIX 4.0 interface

Cheers - Chuck

-----Original Message-----
From: Brendan B. Boerner [mailto:br...@ka...]
Sent: Monday, June 23, 2003 10:17 AM
To: qui...@li...
Subject: [Quickfix-users] QuickFIX and SLK RediFIX?


Hello,

Has anyone used QuickFIX to connect to Spear, Leeds and Kellogg's
RediFIX?

If you have, and could report that QuickFIX worked w/RediFIX w/no
problems, or required some tweaking, I would appreciate hearing from
you.

Regards,
Brendan
br...@ka...




-------------------------------------------------------
This SF.Net email is sponsored by: INetU
Attention Web Developers & Consultants: Become An INetU Hosting Partner.
Refer Dedicated Servers. We Manage Them. You Get 10% Monthly Commission!
INetU Dedicated Managed Hosting http://www.inetu.net/partner/index.php
_______________________________________________
Quickfix-users mailing list
Qui...@li...
https://lists.sourceforge.net/lists/listinfo/quickfix-users

[Quickfix-users] QuickFIX and SLK RediFIX?

[Brendan B. B. <br...@ka...>]

Hello,

Has anyone used QuickFIX to connect to Spear, Leeds and Kellogg's
RediFIX?

If you have, and could report that QuickFIX worked w/RediFIX w/no
problems, or required some tweaking, I would appreciate hearing from
you.

Regards,
Brendan
br...@ka...

[Quickfix-users] YT Luk is out of the office.

[YT L. <yt...@db...>]

I will be out of the office starting  06/19/2003 and will not return until 06/25/2003.

Enjoy!

Regards,

Eric Luk

Equity Technology, Deutsche Bank AG, Hong Kong Branch
mailto : yt...@db...
HK Tel : +852 2203 6348
HK Fax : +852 2203 6973


--

This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and destroy this e-mail. Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden.