On Tue, 24 Apr 2001, Jim Winstead wrote:
> On Tue, Apr 24, 2001 at 11:42:14AM -0700, Justin Erenkrantz wrote:
> > Yup. That is the plan. Somehow use mod_include in mod_mbox. Define a
> > template file and use that each time. That's the goal. Not sure whether
> > we duplicate mod_include or add mod_include to the filter chain (we may
> > want to define our own include syntax - this could define how you want
> > the message or index displayed, headers, footers, etc.). Roy and I have
> > also kicked around the idea of using mod_php as well. Not sure yet.
> well, if mod_mbox actually generated an xml format of some kind,
> you could insert an xslt filter that transformed that xml into html.
> of course, no such xslt filter exists yet, as far as i know.
This is one of the attempts we made at the mailing list archive that
was tested by Covalent Technologies (archive currently down).
It had an XML DTD that was used to transform mbox files into XML and
do XSLT translations on the fly using AxKit/Apache/modperl. You might
want to look at the mod_xslt project or xalan c++ of course.
There was a BOF in Santa Clara for XSLT solutions with Apache, but
sadly I missed it.
You could look at the IETF I-D <draft-klyne-message-rfc822-xml-01.txt>
which came out after our project, but surprisingly resembles roughly
the XML format we used.
Of course parsing XML isn't faster then parsing mbox files, but at
least you can pre-parse MIME attachments and have the ability to apply
any stylesheet you want. One of the hardest areas you run into are
I18N and charset issues, cause most MUAs arent' really good about those.
Cheers,
--
Sander van Zoest [[EMAIL PROTECTED]]
Covalent Technologies, Inc. http://www.covalent.net/
(415) 536-5218 http://Sander.vanZoest.com/
