One reason to not use CGI.pm: An important concern today in the integration architecture is to provide a means to support different type of clients. Unfortunately CGI.pm will not fulfill the increasing requirements to support clients expecting other format than HTML. Such clients can be palm top computers, mobile phones or other device that enables client access.
While there is no hindrance developping differents web components that would generate different presentation format, this solution is costly because it requires additional developement of web component for each distinct client type. These web component also contains very similar logic - they different only in the way they present data - which introduces maintenance problems. Rather than generating HTML pages on the web component tier (CGI.pm), we can generate XML. HTML pages contain information on how to present the data to the web browser. XML, on the other hand, simply describes the semantics of the data - it does not say anything about the preseentation. Afterwards, such XML has to be transformed to a presentation appropriate for the client. This can be HTML for web browser, WML for WAP devices or any other appropriate format. That's here technology like XSLT (eXtensible StyleSheet Language for Transformation) gets into the scene. XSLT engine will tranform the XML to presentation format of your client. There are several XML and XSLT modules from CPAN that can help achiving aforementioned requiremnts, CGI.pm will not ... And this is not a joke :-) My 0.02 José. -----Original Message----- From: news [mailto:[EMAIL PROTECTED] On Behalf Of Tore Aursand Sent: Thursday, November 06, 2003 6:14 PM To: [EMAIL PROTECTED] Subject: RE: Why is parsing your own form data a bad idea? On Thu, 06 Nov 2003 13:21:15 +0100, Jenda Krynicky wrote: >> There is absolutely _no_ reason why one shouldn't use the CGI.pm >> module. > There is one. If /s?he/ is using CGI::Lite instead ;-) In that case, there are many reasons. There are a lot of CGI::* modules out there. My point is still valid, though; Why do one want to use CGI::Lite instead of CGI.pm? Is it better? No. Is it safer? No. Is it faster? No. Is it more widely used? No. Does it come with the Perl distribution? No. -- Tore Aursand <[EMAIL PROTECTED]> -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] **** DISCLAIMER **** "This e-mail and any attachment thereto may contain information which is confidential and/or protected by intellectual property rights and are intended for the sole use of the recipient(s) named above. Any use of the information contained herein (including, but not limited to, total or partial reproduction, communication or distribution in any form) by other persons than the designated recipient(s) is prohibited. If you have received this e-mail in error, please notify the sender either by telephone or by e-mail and delete the material from any computer". Thank you for your cooperation. For further information about Proximus mobile phone services please see our website at http://www.proximus.be or refer to any Proximus agent. -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
