On 10/8/05, wwp <[EMAIL PROTECTED]> wrote: > What else? Splitting logs in daily files and navigate day by day (gaim does > it)? Questions I could see are:
Daily files sounds not so nice... > - what storage format? plain/text, xml, etc. (I vote for a plain text or xml) I was thinking plaintext, but maybe XML is a good idea too. Although, XML will cause the file size to increase with tags. Then on the otherhand, it makes it more easy to read. I guess plain text though.. > - 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!) I'd rather not split the files.. > - 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? Navigate by chunks.. each chunk can be represented by an iterator, similiar to an STL iterator. The only problem is searching... it will be a linear search. If we implement an SQLite DB format, it will be _very_ fast compared to the method used now. Perhaps the SQLite DB format with an option to export to XML is nice... Jon ________________________________________________________ Jon Keating ICQ: 16325723 [EMAIL PROTECTED] MSN: [EMAIL PROTECTED] http://www.licq.org GPG: 2290A71F http://www.thejon.org HOME: Minamiashigara, Japan ------------------------------------------------------- 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
