[Mailman-Developers] Parsing and Rendering rfc8222

[Barry Warsaw]

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

On Jul 5, 2006, at 10:01 AM, Hans G. Ehrbar wrote:

> If mailman would be able to write an xml representation of
> each message to a separate file, that would be wonderful.
> Then one would be able to use xlst stylesheets to make
> custom archives.

It's a very interesting idea.  How resource intensive would an xslt  
transformation be if the messages were vended (and rendered) on  
demand?  Many have advocated such on-demand rendering so that things  
like address obfuscation algorithms could be improved as harvesters  
catch up.  The main argument against this has been server performance  
(that's certainly the reason Pipermail currently generates static  
pages), but maybe through judicious caching this could be amortized  
enough to not crush a server?  I could see a global invalidation  
procedure when something like the obfuscator or a non-stylesheet  
based layout change was made.

Do you have any references for the current state of the art in email  
XML schemas?

- -Barry

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

iQCVAwUBRKxN5nEjvBPtnXfVAQLO1wQAufjZl1Pm7cCLa/Il2zlcdqqPAe4sLzo8
ms1yTaOYaL7z9zB3E0uWv34wZ0+2NZew5WcRnWK8quaOdUYCKQd1TmRzvR7LQa7K
e51wMegx+yqsZOtD1Ug/4mBkHJO2zzhi0Z+/d5S0QkGOzyRNkpDPPJszbpYtVRdz
xdcnahB1RCY=
=e/dx
-----END PGP SIGNATURE-----