Sune wrote:
> 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.
You asked this exact same question to this group a while back. This is
not really a question to do with Standard C, but more of an operating
system issue. You need to consult a group specific for your system.
> I don't want to use TCP/IP client/server between the apps and a data
> store process due to the overhead.
Have you actually measured the "overhead", or are you merely assuming
it's unacceptable?
> 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?
And is this not going impose nearly as much overhead as the other
methods?
> If yes, how do I achieve this? If not, why not?
>
> Thanks for helping out
> /Sune
As I said, this is a general program design issue with connections to
the system's memory and process management facilities. The
implementation language is irrelevant. Consult a more specific group
like comp.programming, comp.unix.programmer, comp.os.ms-
windows.programmer.win32 etc.
--
comp.lang.c.moderated - moderation address: clcm@[EMAIL PROTECTED]
-- you must
have an appropriate newsgroups line in your header for your mail to be
seen,
or the newsgroup name in square brackets in the subject line. Sorry.
|
