Hi! Am 30.05.2006 um 01:00 schrieb Quentin Mathé:
Yes, however I don't think it's a very wise choice to store everything in files, because most file systems have bad performance when you are dealing with huge number of files. I don't really know what is the right choice for Grr. To take an example, for a mail client (dealing with ten or hundred thousand mails quite often) it's a better to store each mail folder or account in a file and write a translator to present them as files in File Manager or to other applications. Bookmarks, contacts or feed articles could be serialized very easily in one file and a simple translator may provide virtual objects by mapping them to precise to XML nodes in the file format (just supposing the serialization is done in XML here, plain text, plist, binary could be better depending on the content).
In the current version of Grr, that's exactly what I do: On exit, Grr serializes its list of Feeds into one single file. Every feed also serializes its list of articles into the same file.
I don't want to keep this, because it turned out to be very slow on startup and exit when using it for some weeks, because the file can become very big.
If I understood your 'translator' concept right, it is about creating "proxy" files representing the articles to make them browsable and searchable in the file manager? I've heard of applications using this (MS Etourage on OSX), but if I understood it right, this is merely a hack to allow Spotlights per-file indexing there.
What's the advantage of storing everything in one big file? I know that NSArray is faster than a file system (because things are already in memory), but I wonder how many articles a user then needs to look at to save time compared to the 'multiple files' scenario.
-Günther _______________________________________________ Etoile-dev mailing list [email protected] https://mail.gna.org/listinfo/etoile-dev
