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.