RE: [Quickfix-developers] trying to test FIX communication Windows C++ code locally

[George D. <mic...@co...>]

Caleb,
Thank you for your reply. Let me now state, that the most important
prerequisite for me with every new programming task undertaken, was to
fully understand the program flow and mechanics of the new task at hand.
If I didn=92t understand that part, I simply couldn=92t put a program
together in a reasonable amount of time, even if I was an expert in the
programming language I was using to do it. I can eventually produce a
program, but only at great cost to me and my employer in terms of trial
and error hours. What I was hoping to avoid here was the excessive
initial hours. I did try the sample programs individually and
scrutinized their source code. However, I didn=92t connect the dots to =
try
the Trade Client program and the Executor program together. It never
occurred to me that these two programs were designed to handshake
locally, not remotely, as this was never explicitly mentioned in the
examples web page. Loading them both with their command line
configuration files as command line arguments was also not even
mentioned. Without the configuration files, the programs would exit as
soon as they came up. I finally adapted all this new found knowledge and
the two programs worked locally in two separate Windows command windows,
and exhibited the program flow and mechanics of operation that I was
looking for. Had two simple sentences explicitly stating how to use the
example programs been supplied on the web site, it would have saved me
many hours of head scratching. So thanks for calling my attention to the
example programs, as it gave me the idea to try them out concurrently.
If I gain any kind of expertise with this FIX programming, I=92ll write =
up
a concise and useful Getting Started type of programmer guide for the
QuickfixEngine website that will eliminate a lot of the guesswork, that
I would bet every new FIX programmer goes through when trying to
implement a FIX communications program for the first time.
=20
In the meantime I still would appreciate a look at anyone else=92s
Microsoft Windows C++ FIX API code, if that programmer is agreeable to
offering that most precious gift of source code to a stranger. I plan to
do the same once I get my source code developed.
Thanks,
George Damusis  =20
=20
-----Original Message-----
From: qui...@li...
[mailto:qui...@li...] On Behalf Of
Caleb Epstein
Sent: Thursday, April 20, 2006 2:42 PM
To: George Damusis
Cc: qui...@li...
Subject: Re: [Quickfix-developers] trying to test FIX communication
Windows C++ code locally
=20
=20
On 4/20/06, George Damusis <HYPERLINK
"mailto:mic...@co..."mic...@co...> wrote:
After supplying a valid sample configuration file for defining the
SessionSettings, and then running the  FIX::SocketInitiator initiator(
theApp, storeFactory, settings ); and  initiator.start(); commands, all
I get is an Exception error from the SocketInitiator.cpp module. This is
obviously due to the lack of a proper connection to a counterparty
acceptor site. I'd love to know how my code can be tested in tight
functional segments on my local computer?
What exception is being thrown?  You have likely forgotten to specify
some required configuration parameter.  You can catch the exception and
print out the result of its what() method for a potentially useful error
message.=20
Any advice from any quickfix developer with experience would surely be
appreciated. In fact I would be very grateful to communicate with a
quickfix developer who has created an initiator side quickfix program
specifically for use in a Microsoft Windows C++ environment.
There are several example programs included that should work out of the
box.  Have you tried using them as a jumping-off point?  See
specifically examples/tradeclient and  HYPERLINK
"file:///C:\\DOCUME~1\\nbde52d\\LOCALS~1\\Temp\\moz-screenshot.jpg"examp
les/executor/C++.

--=20
Caleb Epstein
caleb dot epstein at gmail dot com=20
--
No virus found in this incoming message.
Checked by AVG Free Edition.
Version: 7.1.385 / Virus Database: 268.4.4/319 - Release Date: 4/19/2006

--=20
No virus found in this outgoing message.
Checked by AVG Free Edition.
Version: 7.1.385 / Virus Database: 268.4.4/319 - Release Date: 4/19/2006
=20