Mailing-List: contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-developers-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin-developers AT sources DOT redhat DOT com Subject: RE: fifos and named pipes MIME-Version: 1.0 Date: Wed, 28 Mar 2001 12:21:21 +1000 Content-Type: text/plain; charset="iso-8859-1" Message-ID: content-class: urn:content-classes:message X-MimeOLE: Produced By Microsoft Exchange V6.0.4417.0 Thread-Topic: fifos and named pipes Thread-Index: AcC3LXllPvyGPE52Sm695yihXBdpTQAABhig From: "Robert Collins" To: Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id VAA00153 > -----Original Message----- > From: Christopher Faylor [mailto:cgf AT redhat DOT com] > Sent: Wednesday, March 28, 2001 12:26 PM > To: cygwin-developers AT cygwin DOT com > Subject: Re: fifos and named pipes > > > On Wed, Mar 28, 2001 at 10:46:43AM +1000, Robert Collins wrote: > >Speaking of the glue to see what pipe are available: can I use the > >cygwin shared memory area? any caveats/must dos/must not dos > with doing > >that? > > I'd rather that you open a separate area. I've been slowly > moving things > away from a monothilic shared memory area into separate > areas. For instance, > the user mount table no longer lives there. > > If you use individual shared memory areas, you might be able > to get more > access control, too. > > cgf > Ok. Any known problems with memory mapped files on 95? I'll just store struct in the actual disk after the magic number, and memory map to that file. Access control to the file will be handled by the OS as per usual. Rob