Article View: borland.public.cppbuilder.nativeapi
Article #15940Re: Shared memory question
From: Adam Nellemann
Date: Wed, 04 Jun 2003 22:15
Date: Wed, 04 Jun 2003 22:15
26 lines
2303 bytes
2303 bytes
Hi Guys, Very interesting discussion this (you will excuse me if I allow myself a little amusement on your behalves! Not that what you discusse isn't serious and all, just the number of posts you are reaching in this topic is all!) Without being at all the expert in this area, that you two seem to be, I'll risk my neck in asking this question: Doesn't the Windows SDK come with methods for restricting access to a particular resource in such a way that only the creating process has write access? Is it really necessary with all the stuff you are going into here?!? (again, without actually knowing it) I would have thought that it should be a simple matter of specifying the right security attributes or somesuch, in order to get a handle to a piece of shared memory (or other resource) to which only the current (creating) process is allowed to write, while other processes will only be allowed to read it? Anyway, allow me to use this oportunity to say this to you both: Keep up the good work, nice to have people like you posting so many helpful replies in these fora! Regards, A-)
Technical Details
Message-ID:
<3ede6f7b$1@newsgroups.borland.com>Path:
arc1-ca.pugleaf.net!archiver1.google.com!news1.google.com!sn-xit-02!sn-xit-04!sn-xit-01!sn-xit-09!supernews.com!newsfeed.wirehub.nl!news.kweb.on.ca!KWeb!newsgroups.borland.com!not-for-mailReferences:
<3ec201ad$1@newsgroups.borland.com> <3ec2709a@newsgroups.borland.com> <3ec37cee$1@newsgroups.borland.com> <3ec3c804$3@newsgroups.borland.com> <3ec3ceac$1@newsgroups.borland.com> <3ec41c72$1@newsgroups.borland.com> <3ec4fae5$1@newsgroups.borland.com> <3ec5145f$1@newsgroups.borland.com> <3ec9edca$1@newsgroups.borland.com>Show Full Headers
Complete Article Headers
X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 10cc67,e0ac8188bda6f9e X-Google-Attributes: gid10cc67,public X-Google-ArrivalTime: 2003-06-04 15:18:50 PST From: "Adam Nellemann" <adam@nellemann.nu> Newsgroups: borland.public.cppbuilder.nativeapi References: <3ec201ad$1@newsgroups.borland.com> <3ec2709a@newsgroups.borland.com> <3ec37cee$1@newsgroups.borland.com> <3ec3c804$3@newsgroups.borland.com> <3ec3ceac$1@newsgroups.borland.com> <3ec41c72$1@newsgroups.borland.com> <3ec4fae5$1@newsgroups.borland.com> <3ec5145f$1@newsgroups.borland.com> <3ec9edca$1@newsgroups.borland.com> Subject: Re: Shared memory question Date: Thu, 5 Jun 2003 00:15:23 +0200 Lines: 28 X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 5.50.4922.1500 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4925.2800 NNTP-Posting-Host: 80.62.59.153 Message-ID: <3ede6f7b$1@newsgroups.borland.com> X-Trace: newsgroups.borland.com 1054764923 80.62.59.153 (4 Jun 2003 15:15:23 -0700) Path: arc1-ca.pugleaf.net!archiver1.google.com!news1.google.com!sn-xit-02!sn-xit-04!sn-xit-01!sn-xit-09!supernews.com!newsfeed.wirehub.nl!news.kweb.on.ca!KWeb!newsgroups.borland.com!not-for-mail