Beefy Boxes and Bandwidth Generously Provided by pair Networks
Pathologically Eclectic Rubbish Lister
 
PerlMonks  

(fongsaiyuk)Re: Which is the Best Perl XML Tool?

by fongsaiyuk (Pilgrim)
on Jan 18, 2001 at 09:36 UTC ( #52705=note: print w/replies, xml ) Need Help??


in reply to Which is the Best Perl XML Tool?

maybe you could expand a bit on your thought: My project uses XML::Parser and XML::DOM to do CGI

huh?

If you are rendering XML to HTML and want to use perl, like mirod says, check out AxKit.

If you are just using XML for config file information, you could just stick with XML::Parser and skip the whole Xerces mess. Honestly, I've been watching for the Xerces Perl thing and they've been talking about the "coming soon for RedHat 6.0" for quite a while. I wonder at its state.

For XML with Perl, you should check out davorg's book on "Data Mudging with Perl." He's devoted a chapter discussing perl and XML... It's worth a read as this is, I believe, one of the first books to mention XML and perl and give examples.

IMHO, Java still has a bit of an edge when it comes to XML processing. The great tools at CPAN are rapidly closing that gap though.

Good Luck!

fongsaiyuk

  • Comment on (fongsaiyuk)Re: Which is the Best Perl XML Tool?

Replies are listed 'Best First'.
Re: (fongsaiyuk)Re: Which is the Best Perl XML Tool?
by sierrathedog04 (Hermit) on Jan 18, 2001 at 22:34 UTC
    maybe you could expand a bit on your thought: My project uses XML::Parser and XML::DOM to do CGI

    We have an online database update application. The boss knows the client is very interested in XML. He suggested I write a new screen that was needed and use XML to do it.

    My preference would have been to assume that the user had an XML-compliant browser such as IE5. However, we are required to target our code for IE4. So I:

    1. Use javascript on the client side to format the update data as one long string of XML and submit that.
    2. Use XML::DOM to parse the XML string and submit it to the database. SQL queries are coded so that they return valid XML.
    3. Return this database-generated XML if the user has checked a box on his form requesting XML output. Otherwise, Use XML::DOM to parse this database-generated XML.

    I should have used XSLT to transform the XML into XSLT. However, last December the XSLT module on www.cpan.org seemed not to work. I want to thank the Dutch university students who appeared to be writing it but it simple was not ready.

    Since then a new XML::XSLT module has appeared. I have not looked into it.

    So that is what I meant by using XML to do CGI. Did we need to use XML? Not really. However, I believe that there are advantages to doing so. For instance, since our application offers the option of returning XML, it would be easy to write a client-side add-on to do more complex processing on the client side.

Log In?
Username:
Password:

What's my password?
Create A New User
Node Status?
node history
Node Type: note [id://52705]
help
Chatterbox?
and the web crawler heard nothing...

How do I use this? | Other CB clients
Other Users?
Others romping around the Monastery: (5)
As of 2018-08-20 23:48 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?
    Asked to put a square peg in a round hole, I would:









    Results (197 votes). Check out past polls.

    Notices?