Re: Spawning a subprocess and communicating with it.

["alan walkington" <walky@netmagic.net>]

Marin:

Alas, you will have to give up the pipe....
I don't believe the simple soulution will work across the network.  I think
pipes will only work if you
are on the same machine.

It is indeed time to look at sockets, or perhaps RPC's.

If you want the code to be portable to other than GNAT compilers, you should
probably look at the posix library.

Isn't it strange how the simplest of projects grows more and more convoluted
over time?

Alan Walkington
walky@netmagic.net

Condic, Marin D. wrote in message ...
>Thanks for the reply. Looking at the GNAT code in the GNAT.OS_Lib package,
>it's "Non_Blocking_Spawn" function degenerates to a C call after massaging
>some parameters. Someone sent me an example of how to do this with Unix
>calls, but then you've got something that can't automatically correct
itself
>if moved to the PC.
>
>Unfortunately, I do have to have two separate processes. The problem is
that
>the client and the server have to be separate programs since the server
>could be either another process running on the workstation, or on a
>different workstation, or an embedded application in my engine control
>computer. I need to design the connection so that the same program - or one
>with slight variations - can talk to the simulated embedded machine or the
>real embedded machine. I figure that breaks down into processes and pipes
at
>the workstation end.