FWIW, I vote for storing it in a database. By using MyISAM files and splitting on listname/time, you can build lots of smaller files and use merge tables to dynamically throw them together as needed, without building really bloody huge tables. a nice compromise, but you get all sorts of fun stuff that way, easy dynamic indexing, some usable search engine stuff, etc....
On Oct 27, 2003, at 2:03 PM, Barry Warsaw wrote:
Chuq made some convincing arguments that even public archive access
should go through a script. By generating the viewed archive message on
the fly, from its native source, we'd have all kinds of control over the
presentation. Such as: changing the address obfuscation rules on the
fly, the ability to retract or re-publish archive messages on the fly,
more advanced threading options, no artificial date divisions, the
ability to change the look and feel easily, etc. With proper caching
machinery and the use of more modern programmatic fulfillment of web
requests (e.g. mod_python, twisted, etc.), this should be efficient
enough.
_______________________________________________ Mailman-Developers mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-developers
