[Mailman-Developers] Apache configuration: Web Interface for archives in mm3

[Barry Warsaw]

On May 15, 2011, at 06:15 PM, Benedict Stein wrote:

>Did i understand something incorrectly or is the Django UI only a config
>website ?

That is currently the case, yes.

>Why don't we have all UI parts within the Django project (which I'll support
>during gsoc ;-))

It's a good question.  There are two things that will influence design
decisions for Pipermail's web ui.  First, I would eventually like to split
Pipermail into a separate sub-package of Mailman, so that it could be used
independently, or easily thrown out if someone wants a different archiver.  It
would also allow Pipermail to advance on a different schedule than the core
engine.

Second, Pipermail has always generated static HTML files, so the "web ui" such
as it is, is basically just Apache vending those static HTML files.  Now, I've
long thought that it would be better, and technically feasible, to generate
the archive HTML on the fly, when a message is requested (with appropriate
caching for performance).  Doing dynamic generation of those pages would allow
for some interesting ideas, such as changing content filtering more easily
(e.g. address obfuscation, hyperlinking special text like bug numbers, etc.).
But that's also a major redesign of the Pipermail architecture.

-Barry
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: not available
URL: <http://mail.python.org/pipermail/mailman-developers/attachments/20110516/b5e9d98e/attachment.pgp>