Hello Jon,
On Fri, 7 Oct 2005 23:37:32 +0900 Jon Keating <[EMAIL PROTECTED]> wrote: > On 10/7/05, Nikita Bige <[EMAIL PROTECTED]> wrote: > > I think the problem in reading the _whole_ history files. > > Every time when the new window pops up (according to programm top) > > utilized memory increase by ~6mb. > > How I can help to find the problem? > > Don't show the last recent messages when you open a dialog.. it's in > the options. "Show recent messages". > > The problem is as you said, the whole history file is read. This is > one of the things that is planned to be changed in the future, but I > haven't decided how to implement this. I like the idea of keeping it a > text file, it makes it easy to do cool stuff with it using basic > tools. Perhaps I'd implement it as reading chunks at a time.. the > chunk being requested. What else? Splitting logs in daily files and navigate day by day (gaim does it)? Questions I could see are: - what storage format? plain/text, xml, etc. (I vote for a plain text or xml) - log file split or not? (no preference, current implementation is like mbox, the more it grows, the worst the performances are - unless you index the contents, which is not a good idea - keep it simple!) - history navigation: what to load? how to navigate in the logs? Does the navigation (the GUI) reflects the file split or does it splits differently? Just thinking.. Any other thought? Regards, -- wwp ------------------------------------------------------- This SF.Net email is sponsored by: Power Architecture Resource Center: Free content, downloads, discussions, and more. http://solutions.newsforge.com/ibmarch.tmpl _______________________________________________ Licq-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/licq-devel
