🚀 go-pugleaf

Another (? - don't know what you have) example that I've found to be a 
simple reference:
http://www.codeproject.com/KB/threads/csharedstruct.aspx

However, comments in the code specifically indicate that author had trouble 
trying to figure out how to use security ACLs to obtain results of the 
nature you desire (with some processes having only read-access and other(s) 
having more)...

But maybe it will clarify what area you need to look at.

(Also note that the class as presented there does not set its member 
variable m_bCreated, which might be useful in some cases.)

As to whether the mutex is necessary, that would depend on you - if you need 
to write multiple things that have to be "consistent" with one another, then 
a mutex probably would be necessary.  If any modified item is exclusively 
valid, than no mutex should be required (given that you want only one 
process to write to the area.)

"Mike Collins" <its@TheBottomOfThePost> wrote in message 
news:48500053@newsgroups.borland.com...
>
> Having read a bit about this, it seems that a Memory Mapped file would be 
> the easiest option.  So I'm just experimenting with Mem Mapped Files and 
> there's a few things that I don't quite understand.  I need my service to 
> be able to read and write to the MMF but I don't want any other process to 
> be able to modify it...
>

>
> 5) I'm looking at a code example in VC++ and the author seems to have used 
> a mutex to control access whilst reading or writing - is this necessary?
>
> Sorry about the length of questions, and pointers or suggestions would be 
> gratefully received.
>
> Many thanks,
>
> Mike
>