[Mailman-Developers] email schema / XSLT

[Barry Warsaw]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Jul 6, 2006, at 10:16 PM, Bob Puff at NLE wrote:

> One thing that I find very disappointing is to (google|yahoo\fav  
> search) a solution to a problem,
> only to find that the message that looks promising is in an archive  
> that has been either nuked,
> moved, or reindexed, so you can no longer see the original  
> message.  Yes, Google's cache does help
> out a lot, but if you want to start reading the threads, it breaks  
> quickly.

I agree.  Sadly, Pipermail's original message id algorithm (and the  
one we still use) is extremely fragile, and in fact, due to archiving  
bugs in the past, if you were to regen your archive even now, you'd  
probably break links.

> If there was =any= way you could also include in your XML perhaps  
> the original message id that the
> older pipermail created, you could then render those messages on  
> the fly with the appropriate
> scripting, and even keep old URL links (perhaps under a 'legacy  
> link' program or something).

I think it's a great idea.  Have to think about how/if that's even  
possible.

> This brings up the next question: how are these messages to be  
> stored?  If its flat files, its gonna
> take a lot of processing if you have to render these on-the-fly.

I'm sure you'll want to cache the pages, with ways to chuck the cache  
at various times (e.g. globally when the email obfuscation algorithm  
is modified for a site).

- -Barry

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (Darwin)

iQCVAwUBRK3fQ3EjvBPtnXfVAQJIGQP+MxXjiRSPgNRyzEYb6OfZB5jKBM4Cyht+
Ozymw/qoZeQ0qop2BTkywYmiqKY/Sq0k9cBlDSt8SJJ2ULzVw9WKABCjyZpAjghw
FSWRdrX/ElMpEiQibjAPo9vH0fujybhZX0tJhygZTEt+RSeL9l9IC+acH+tKf2VA
UnYUEMk6rmo=
=UR+F
-----END PGP SIGNATURE-----