Re: Dynamic C to C Data Transfer


Tom <Thomas-911@xxxxxxxxxxxxx> wrote in message
news:6e5ao2lcbal3ofomguqaro5udd98env0he@xxxxxxxxxx
On Sun, 17 Dec 2006 08:15:46 +0000, Richard Heathfield
<rjh@xxxxxxxxxxxxxxx> wrote:
Tom said:
On Sat, 16 Dec 2006 23:33:27 +0000 (UTC),
gazelle@xxxxxxxxxxxxxxxxxxxxx (Kenny McCormack) wrote:
In article <45845237.1596155@xxxxxxxxxxxxxx>,
Roland Pibinger <rpbg123@xxxxxxxxx> wrote:
On Sat, 16 Dec 2006 18:11:49 GMT, Tom wrote:

The scenario is: Several networked machines. Each performing stock
analysis on individual or a small group of financial instruments and
then passing buy/sell instructions to an order placing machine.

Is the platform, by any chance, Windows?
If so, try using INI files. Works real well.

Thanks for the tip Kenny.

It's a tip that doesn't do you any good, though, always assuming your
problem isn't that of opening and writing and reading and closing the
files. For that, any old format will work. But the advice is no more than
we'd expect from Mr McCormack.

The proper way to do this is via sockets, but yes, you could hack at it
with
files if you wanted, if you wanted something short-term while you were
busy
learning sockets.

Thanks for your incite Richard.

LOL!!! Thanks for the entertaining spelling!

Of course, all of this sounds like classic job for something like
"remote procedure calls" (RPC) just off the top of my head, so
I typed "remote procedures" into the Google(TM) search
box on my ISP home page and got about 128,000 links in
0.14 seconds.

The top link seems to contain a lot of the "C" code needed
to implement client-server RPC, so check it out and see
if this is what you want:

http://www.cs.cf.ac.uk/Dave/C/node33.html

Or if the ACTUAL problem you are trying to solve can BE
solved BEST by using RPC (note carefully the description of
RPC in the first paragraph of the link, particularly the part
about "network transport independence" in light of the
advice here about "sockets"). I'm not completely sure from
your description if that is even the case (except you seem to
require a "lock" to prevent multiple use of the same file), but if it is,
I would think that somewhere in the 128,000 or so links, you'll
have enough to proceed, or at least think about...

Now "RPC" is kind of a generalized concept that sort of came
out of other concepts such as "distributed computing", and that
it was implemented in Unix as "CORBA", and be aware
that Microsoft has their own version of it (naturally) that has gone
through several versions...I've used what they call "DCOM" in the
past, so you might want to look at that on the MSDN site (or cite!)
for stuff like that...

In any event, back the regularly-scheduled flame war!

---
William Ernest Reid



.

Relevant Pages

  • Re: Dynamic C to C Data Transfer
    ... gazelle@xxxxxxxxxxxxxxxxxxxxx (Kenny McCormack) wrote: ... "remote procedure calls" (RPC) just off the top of my head, ... It's google time for me. ...
    (comp.lang.c)
  • Re: Dynamic C to C Data Transfer
    ... analysis on individual or a small group of financial instruments ... "remote procedure calls" (RPC) just off the top of my head, ... For now I consider RPC, sockets, file writing hack, and INI techniques ... appear to be working on (a distributed automatic stock trading ...
    (comp.lang.c)