I'm just using XML on the backend for content management and as
a way to standardize what I recieve from partners and content folks,
then storing parsed content in a database from which I output text, HTML,
and/or XML.
XML::Parser suits quite fine for the above. So, Perl has plenty of XML support,
imo.
I've taken a look at what Matt is up to and I'm intrigued, but don't have a need
for it as yet.
Joshua, what is the itch that you are scratching if you care to opine?
Ed
Drew Taylor wrote:
> Joshua Chamas wrote:
> >
> > Perrin Harkins wrote:
> > >
> > > On Fri, 9 Jun 2000, Drew Taylor wrote:
> > > > I really like the fact that templates can be compiled to perl code &
> > > > cached. Any others besides Mason & EmbPerl (and TT in the near future)?
> > >
> > > Sure: Apache::ePerl, Apache::ASP, Text::Template, and about a million
> > > unreleased modules that people wrote for their own use. (I think writing
> > > a module that does this should be a rite of passage in Perl hacking.)
> > >
> >
> > For my second rite of passage, I'm hacking XML::XSLT
> > integration into Apache::ASP for realtime XSLT document
> > rendering with a sophisticated caching engine utilizing
> > Tie::Cache. Moving forward, the XML buzzword seems to be
> > just about a necessity.
> >
> > Take it as a sign of respect Matt :)
> Cool! The thing that perl is missing the most right now is XML support.
> The more (and the sooner :-) packages support XML easily and natively,
> the better. I'm still an XML newbie, so all this recent perl XML
> development is very exciting for me!
>
> --
> Drew Taylor
> Vialogix Communications, Inc.
> 501 N. College Street
> Charlotte, NC 28202
> 704 370 0550
> http://www.vialogix.com/
