On Sun, 19 Oct 2003 19:26:59 -0400 (EDT) Richard Welty <[EMAIL PROTECTED]> wrote:
RW> in server administration, they've been expected parts of a well administered RW> un*x system going back well into the 90s, if not before. RW> RW> the tradeoff is this -- a file such as a newsrc file often has tens of RW> thousands of lines representing newsgroups. you can read it all in, and RW> represent it RAM, (slow startup and memory consumption) or use a DB and RW> only access what you need. RW> RW> on reflection, you do need to read the whole thing, flat file or DB, just RW> to find out what you're subscribed to, so the DB file savings are an RW> illusion as a replacement for newsrc. RW> RW> what might be good is to retain newsrc, but since there are a number of Yes, a text .newsrc is a bit of a standard although for the most part you do only tend to need the parts relating to the groups you are subscribed to. If you kept those parts elsewhere, it would only really affect people using the same .newsrc for multiple newsreaders wouldn't it? RW> characteristics of a newsgroup and articles you might keep beyond just RW> subscribed/unsubscribed and read/unread, put that stuff in a DB file. Have you done any performance tests comparing their XML version to the standard version? I'm wondering how it scales for thousands of items? On one of their www pages they have a comparison of the various versions supposedly including XML but it was not included so I sent them a headsup and got a nice thanks message so hopefully Marketing will fix it soon :-) ------------------------------------------------------- This SF.net email sponsored by: Enterprise Linux Forum Conference & Expo The Event For Linux Datacenter Solutions & Strategies in The Enterprise Linux in the Boardroom; in the Front Office; & in the Server Room http://www.enterpriselinuxforum.com _______________________________________________ Mahogany-Developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/mahogany-developers
