Re: IPC mechanisms under Linux

On Sep 24, 7:28 am, Wellu <kuumaliimam...@xxxxxxxxx> wrote:
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.
[snip]
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.
[snip]
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.

There are many IPC mechanisms that might satisfy your problem.
For data passing, you can use
- files,
- unnamed pipes,
- named pipes,
- UNIX sockets,
- TCP/IP sockets,
- shared memory,
- Posix message queues,
- DBUS
For signalling, you can use
- sentinal files
- file locking
- signals
- files/pipes/sockets and poll/select
- semaphores
- message queues
- DBUS


.

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)
  • IPC mechanisms under Linux
    ... listens for incoming messages or events. ... that are controlled by this Engine. ... At the same time Engine can ... "Run Module 10 again" Modules could also send messages to upper levels ...
    (comp.os.linux.development.apps)