Nadav said:
You are welcome.
I wonder... Concerning the shared mem mapping is
the first thing I do on process startup, doesn't
existing memory layout of multiple process may
include cases where no two processes may have
the same memory block mapped to the same
address, e.g. a memory block of about 0.25GB is
about to be mapped to the same address of several
process ( using MapViewOfFileEx ), is it possible
that no continues memory block at the same address
( in each process ) can be found for all process, what
is the feasibility for such a scenario?
I should have been clearer but yes, it is possible that two processes may
not be able to share the same sized block at a common "virtual address". The
point is that the mapping is "per-process". Unlike the case on 9x, it is a
process' view of the shared memory which is associated with an address. On
9x, the shared memory block itself is associated with the shared address.
I guess I would have to implement some hand-shake
mechanism to achieve this task ( in case it is feasible )...
Yes, you could do that.
I would, however, suggest that you not store pointers in the shared memory.
That's because unless those pointers reference locations in the shared
memory, they are invalid outside of the process that "created" them. In
other words, you can only share references to what is truly shared.
So,
if you find a need to share pointers you would store offsets from the start
of the shared memory instead. In that way, each of the processes mapping the
memory could map at any convenient address.
Regards,
Will