S
Sune
Hi all,
I want to make data stored in-memory (not disk) available to several
processes. My concern is that poorly written C applications with
dangling pointers may(will) damage the data in this memory segment if
it is open to all, i.e. shared memory mapped into all processes memory
area.
I don't want to use TCP/IP client/server between the apps and a data
store process due to the overhead.
I don't want to start calculating checksums for all updates in a
shared memory area, since that means a lot of overhead.
Now my question:
Is it possible to expose just the interface of a data store component
and have that i/f shared between all processes who want to access the
data, and then have this shared interface make callbacks into a data
store process' private memory?
If yes, how do I achieve this? If not, why not?
Thanks for helping out
/Sune
I want to make data stored in-memory (not disk) available to several
processes. My concern is that poorly written C applications with
dangling pointers may(will) damage the data in this memory segment if
it is open to all, i.e. shared memory mapped into all processes memory
area.
I don't want to use TCP/IP client/server between the apps and a data
store process due to the overhead.
I don't want to start calculating checksums for all updates in a
shared memory area, since that means a lot of overhead.
Now my question:
Is it possible to expose just the interface of a data store component
and have that i/f shared between all processes who want to access the
data, and then have this shared interface make callbacks into a data
store process' private memory?
If yes, how do I achieve this? If not, why not?
Thanks for helping out
/Sune