Re: Interprocess Communication...
On Wed, 10 Nov 2004 17:49:26 -0600, Kat <gertie at visionsix.com> wrote:
> <snip>
> > The main thing is - if a program crashes when one of its functions is
> > called remotely, does it crash the calling program, and can the
> > calling program detect that the other program crashed?
>
> There are ways, i forget how, to detect if any program is running. Also to
> kill
> it. Code is in the archives. Detecting if the module is sitting there with a
> dos
> box and whining that you must press <enter> , i don't know. If you want to
> maintain if the spawned modules is running, it should either send a ping or
> respond to one periodically. Or be doing something else that can be
> detected by the main process externally. For my mirc-eu, i pinged with a
> number representing the time, pretty much like irc does anyhow.
Yes, it would be nice to be able to close the euphoria error console
that appears when an error occurs.
I'd _rather_ not need some kind of heartbeat function to make sure the
thing still works...
The main process wouldn't really be running - I can't quite tell, but
I think the IPC library is synchronous. That is, once a remote
procedure/function is called, it doesn't return until that procedure
is finished.
Maybe I need to implement a custom communications system.... *grumbles*
--
MrTrick
|
Not Categorized, Please Help
|
|
