On Tue, Feb 26, 2002 at 08:57:38PM -0600, David Champion wrote: > Or, since the archiver is an integrated part of Mailman already -- this > is presupposed in the context of this thread -- I can have the archiver > perform some basic searching. That's easy on the user, because it's a > single authentication transaction to get into the archive and to perform > a search. (With the other approaches, it's two transactions, unless the > new code knows not only how to talk to Mailman's roster, but also how > to insert an authentication token into the HTTP client in a forward- > compatible way.) That's also a bit of work, but it doesn't need to be > high-powered searching. Just basic "find this text" will do for most > purposes. And it has the advantage of being more integrated with the > MLM, requiring less off-sync third-party maintenance. I'm interested > in a 95% solution. And it's there and useful with environments besides > Mailman, too, even if they also use odd built-in authentication systems > that aren't a part of the local web server. > > Maybe I'm still missing something, but if so, I still don't see it.
I believe that what you're missing is up in the top of the message -- unless *I'm* missing something. Pipermail is *not*, so far as I've been able to tell, "an integrated part of Mailman". Is it, Barry? For the purposes of David's assertion above, I mean. Cheers, - jra -- Jay R. Ashworth [EMAIL PROTECTED] Member of the Technical Staff Baylink RFC 2100 The Suncoast Freenet The Things I Think Tampa Bay, Florida http://baylink.pitas.com +1 727 647 1274 "If you don't have a dream; how're you gonna have a dream come true?" -- Captain Sensible, The Damned (from South Pacific's "Happy Talk") _______________________________________________ Mailman-Developers mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-developers
