IPC mechanisms under Linux

Hi all,

I'm trying to develop a system for Linux platform that consists of
several different parts. Firts of all there would be Engine part that
listens for incoming messages or events. Then there is several modules
that are controlled by this Engine. Let's call these merely Modules.
Modules could then call other APIs or create processes. Once Module is
done it returns and Engine knows that particular Module is done
processing. There can be several modules (e.g hundreds) running at the
same time so everything is asynchronous. At the same time Engine can
get new messages from upper levels using some IPC mechanism. For
example there might be message saying "Pause Module 1 for 10 secs" or
"Run Module 10 again" Modules could also send messages to upper levels
(e.g by calling simple API) and wait for responses. So, all in all
Engine must listen to events from Modules and from upper levels.

Engine and Modules run in the same machine and programming language
would be C.

--
Wellu

.

Relevant Pages

  • Re: IPC mechanisms under Linux
    ... listens for incoming messages or events. ... that are controlled by this Engine. ... "Run Module 10 again" Modules could also send messages to upper levels ... , I'd say the standard networking API would be appropriate, select/poll thrown in to aid in keeping the lid on the zoo of connections. ...
    (comp.os.linux.development.apps)
  • Re: IPC mechanisms under Linux
    ... listens for incoming messages or events. ... Engine must listen to events from Modules and from upper levels. ... Posix message queues, ... For signalling, you can use ...
    (comp.os.linux.development.apps)
  • Re: IPC mechanisms under Linux
    ... that are controlled by this Engine. ... Modules could then call other APIs or create processes. ... At the same time Engine can ... "Run Module 10 again" Modules could also send messages to upper levels ...
    (comp.os.linux.development.apps)