> Shared memory basically allows you to share a chunk of memory.
> You protect access to this chunk by using a semaphore.
> Depending on how you use the semaphore, you may also need to use
> a single signal to inform the other process that it has a
> message waiting inside the shared memory.
I agree with Christopher, shm + sem is IMHO the better solution.
Inside XMail tarbal ftp://ftp.maticad.it/pub/misc/mailsvr.tar.gz You'll find
the code
to handle this kind of data structure in a system independent way ( Linux &
Win32 ).
Davide
-- Feel free, feel Debian !- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Fri Jun 23 2000 - 21:00:25 EST