[prev in list] [next in list] [prev in thread] [next in thread]
List: kde-devel
Subject: Re: reading mimetypes fast
From: Sirtaj Singh Kang <ssk () physics ! unimelb ! edu ! au>
Date: 1999-06-09 7:39:55
[Download RAW message or body]
On Wed, 9 Jun 1999, Alex Zepeda wrote:
> On Tue, 8 Jun 1999 pbrown@redhat.com wrote:
>
> > I don't see what is the problem with having one program (something like
> > the trader I guess, except I am so corba-unaware I have no clue wtf the
> > trader is) that reads all the mimetypes at startup, and then we use the mm
> > library / shared memory for all other programs to get information from
> > this program? Eliminates tons of repetitive memory consumption and IO,
> > and puts everything in a nice clean unified location.
>
> I think the mm library will only work between parent and child processes?
I gathered that from the docs too, but on closer inspection of the API it
looks like shared spaces are named with normal filenames (that don't
necessarily exist), so I assume that if two programs use the same filename
for the segment, they share the associated memory. But I could be wrong.
-Taj.
Sirtaj S. Kang taj@kde.org ssk@physics.unimelb.edu.au
Univ of Melbourne
"I'm a commercial operating system."
-Doug Michels (CEO SCO)
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic