Re: Writing a GNOME mail client.

[Scott Wimer <scottw dev cgibuilder com>]

Nathan,

in the model that I talked about (each Message is a file, separate
index file for each Group of Messages), we won't endup with that
many open files.  The inode count could become an issue of concern
though.  But, we've got to have a whole lot of messages stored to
run out of inodes.  

We've really only got 2 options to us, each Message in a single file,
or some aggregation method for putting multiple Messages into a single
file.  Any aggregation method is going to take some additional
algorithmic complexity to handle.  Maybe, if all the Messages for a
given day were placed into a single file, that would make them fairly
easy to retrieve, since we can resolve the storage file from the 
Message ID rather painlessly.

I don't have any thing that I'd call a silver bullet on this one
though.:(

regards,
scottwimer

On Mon, 19 Apr 1999, Nathan Clegg wrote:

> 
> By giving every message its own file and even splitting a single message
> into several files, don't we risk running out of inodes on a multi-user
> system??  I collect hundreds of messages every week from my 15+ mailing
> lists, compared to the thousands I throw away.  Aren't we also seeing a
> performance hit if we have to open multiple files everytime we scroll to a
> single message, or likewise if we have to read, say, 1000 files to open a
> single folder?
> 
> Warren Young wrote:
> > Distilled, my view is that there are two models to choose from: the
> > Windows Registry and CVS.  Me, I'd prefer the CVS approach.
> 
> 
> ----------------------------------
> Nathan Clegg
>  nathan@islanddata.com
> 
> 
> 
> -- 
>         FAQ: Frequently-Asked Questions at http://www.gnome.org/gnomefaq
>          To unsubscribe: mail gnome-list-request@gnome.org with 
>                        "unsubscribe" as the Subject.
> 
> 

--
Scott Wimer
play  --->    scottw@cgibuilder.com         http://www.cgibuilder.com/
work  --->    scottw@corp.earthlink.net     http://www.earthlink.net/