Hi,

As stated ikegami, you will need to run a server on the other side, which will launch/executes the other processes by forking/threading.

A simple example would be a daemon/webservice which listen on a given port, the cgi contact with this daemon and do RPC to instruct the remote process what program or actions to do. For communication between this two processes I would recommend you XML-RPC, it's very simple with the benefits that the information is xml -> text, so the debugging is very simple. If you need some security above this you could make the communication through a secure tunel.

Take a look at the website, there is a very good howto with code examples for the most used programming languages

I don't really know how complex is the thing you are creating, but if you have a Jabber server inside your company, or had think about using one, you could also use the Jabber server as a message-server for passing the RPC calls to the remote process that is online in the Jabber server, with the benefits that the process is like a service or client of the Jabber server, and having all the security/reliability that the Jabber server can give you... only a idea, but... could be interesting for you. So you can "talk" with the service/client as it were a human. ;-)

Regards,