At 4:06 PM -0400 2006-06-07, Barry Warsaw wrote:
> Ultimately, I think generating the archive html on the fly is the right
> way to go. That approach provides so many possible benefits at the
> mere <wink> cost of cpu time. When the original archive system was
> designed, that cost was too high, and thus we have the static page
> rendering approach. But today I think the tradeoff tips in the other
> direction.
I think we need to have both solutions. I have some really
anemic machines running Mailman, and I can't imagine what they'd do
if they had to generate HTML archives on the fly.
> As I always say when this topic comes up, I'd love to have some
> motivated developers come forward to help with an archiver redesign, so
> if you're interested in doing work here, let me know!
I can give some input and feedback based on my own experiences,
but I'm not a developer. ;(
--
Brad Knowles, <[EMAIL PROTECTED]>
"Those who would give up essential Liberty, to purchase a little
temporary Safety, deserve neither Liberty nor Safety."
-- Benjamin Franklin (1706-1790), reply of the Pennsylvania
Assembly to the Governor, November 11, 1755
LOPSA member since December 2005. See <http://www.lopsa.org/>.
_______________________________________________
Mailman-Developers mailing list
Mailman-Developers@python.org
http://mail.python.org/mailman/listinfo/mailman-developers
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives:
http://www.mail-archive.com/mailman-developers%40python.org/
Unsubscribe:
http://mail.python.org/mailman/options/mailman-developers/archive%40jab.org
Security Policy:
http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.027.htp
