RE: [Quickfix-developers] FIX message Parser and FIX Message Composer

[Rob K. <ro...@ri...>]

Yes if does.
parse them:
http://quickfix.thoughtworks.com/documentation/receiving_messages.html
=20
compose them:
http://quickfix.thoughtworks.com/documentation/sending_messages.html
=20
I hope this helps.  Good luck.

-----Original Message-----
From: Vamsi Krishna [mailto:Vam...@ib...]
Sent: Friday, February 28, 2003 11:09 AM
To: Rob Kulseth
Subject: RE: [Quickfix-developers] FIX message Parser and FIX Message =
Composer



I did ..just now.. after downloading the stuff.

Does it specifically mention any where how to use the library to parse =
fix message or compose fix message..?

=20

Vamsi

=20

-----Original Message-----
From: Rob Kulseth [mailto:ro...@ri...]=20
Sent: Friday, February 28, 2003 12:00 PM
To: Vamsi Krishna
Subject: RE: [Quickfix-developers] FIX message Parser and FIX Message =
Composer

=20

did you even look at the documentation?

-----Original Message-----
From: Vamsi Krishna [mailto:Vam...@ib...]
Sent: Thursday, February 27, 2003 6:25 PM
To: qui...@li...
Subject: [Quickfix-developers] FIX message Parser and FIX Message =
Composer

Hi

Can I use quickfix.lib to compose a fix message ( I am using C++ version =
of quickfix) and if I can.. how to do it?

=20

Also Can I parse the fix message into object ( say Market data request  =
fix message to a class of Market data request object )

=20

How do I begin

=20

Can somebody help me out.=20

Vamsi

=20

=20

-----Original Message-----
From: qui...@li... =
[mailto:qui...@li...] On Behalf Of =
Bernard Spanger
Sent: Thursday, February 27, 2003 6:16 PM
To: qui...@li...
Subject: [Quickfix-developers] Problems migrating from 1.0.4 to 1.3.2

=20

This week, I finally decided to upgrade from 1.0.4 to 1.3.2 to see how =
it went.  I have a server application and a client application.  The =
server application needed only 1 small change to make it compile.  The =
first arguments to the following 2 functions appear to no longer be =
const:

=20

  void toAdmin( FIX::Message&, const FIX::SessionID& ) {}
  void toApp( FIX::Message&, const FIX::SessionID& )

=20

I'm pleased to say that once I made the change, my server application =
compiled and ran through all the scenarios I tested without problems.

=20

My client app has another problem.  It required the same changes, but =
once made, it started blowing up right at the line shown below.  For =
some reason, it is unable to find the session in the collection.  I'll =
trace through tomorrow to see what's going on, but if anyone is aware of =
a change between these releases that would save me the time, I'd be very =
grateful!

=20

=20

bool Session::sendToTarget( Message& message )
throw( SessionNotFound& )
{
  try
  {
    SessionID sessionID =3D message.getSessionID();
    Session* pSession =3D lookupSession( sessionID );
    if ( !pSession ) throw SessionNotFound();    =
----------------------------------------------------------> Right here!
    bool result =3D pSession->send( message );
    return result;
  }
catch ( FieldNotFound& ) { throw SessionNotFound(); }
}

=20

=20

------------------------------------------
Bernard Spanger
bsp...@gx...
G. X. Clarke & Co.
10 Exchange Place
Jersey City, NJ 07302
201-200-3607

=20


  _____ =20


Confidentiality. This message (including any attachments) (collectively, =
the "Material") may contain confidential information and is intended =
only for a specific individual and purpose. If you are not the intended =
recipient, any copying, disclosure, distribution or other use of the =
Material, or the taking of any action in reliance on the information =
contained therein, is strictly prohibited. If you have received the =
Material in error, please immediately notify us by telephone and delete =
the Material and all copies thereof from your computer and network.

No Investment Advice, Offer or Solicitation; Suitability. The Material =
has been prepared for informational purposes only without regard to any =
particular user's investment objectives, financial situation or means =
and does not constitute an offer, solicitation or recommendation to take =
any action. We are not providing investment advice, nor do we represent =
that any securities or services described in the Material are suitable =
for a particular client. Before acting on the Material, each client =
should make its own determination whether information contained therein =
is suitable for its particular circumstances, and if necessary consult =
with a senior officer.

Conflicts. We, or persons involved in the preparation of issuance of the =
Material, may from time to time effect transactions, or have positions =
in the securities mentioned in the Material (or options or futures =
contracts with respect thereto).

Disclaimer. Although the Material is based upon information that we =
consider reliable, we do not warrant that the Material is reliable, =
accurate or complete and it should not be relied upon as such. Neither =
we, nor any of our affiliates or agents shall have any responsibility =
whatsoever for any direct, indirect, consequential, special or other =
damages or lost profits or savings or other economic harm your may =
suffer as a result of your reliance on the Material or the reliability, =
accuracy, or completeness thereof. We expressly disclaim all express and =
implied warranties, including, without limitation, warranties of =
merchantability and fitness for a particular purpose.

---------------------------------------------
-Checked for viruses by McAfee.- o1
---------------------------------------------=20