Andreas Ebneter (
fudima...@gmx.net) wrote:
> Hi,
> I'm new to system programming and I should decide what kind of interprocess
> communication (signals, shared memory, message queues, pipes, named pipes,
> sockets, STREAMS, SMTP etc. or combinations) is most suitable for resolving
> our problem. We work on the Solaris operating system. The whole application
> will run on one single Sun server.
>
> * We need asynchronous or non-blocking
> calls
> * The communication has to be fast with
> negligible latency
> * The communication must not result in high
> system load
> * We need to transmit some data, +/-128 bytes
> * Implementation has to be as easy
> as possible, because I'm a newby...
> * Some calls have higher priority than others
> and must be answered faster
>
> What kind of interprocess communication do you recommend?
> Why? What are the advantages? What are the drawbacks?
Standard System V message queues will do just fine. Look at the
msgget, msgctl, msgsnd and msgrcv man pages.
--
Aleksandar Milivojević <al...@fly.srk.fer.hr>
Opinions expressed herein are my own.
Statements included here may be fiction rather than truth.