Hi Cees -- > I don't think there are any planned new additions to Apache::Request, > and it has been stable for years. To say it is incomplete because it > doesn't support all the features of CGI.pm is not really fair, since > they both serve a different purpose.
You're right -- I should have clarified. I was referring to the fact that it's not a drop-in replacement for CGI.pm. IOW, if CGI-App changes to give the user a Apache::Request object instead of a CGI.pm object (without telling them) then code is going to break. I don't really think Apache::Request serves a different purpose from CGI.pm, however. Both are high-level interfaces to HTTP, and both are used to making web-apps. The fact that Apache::Request does not include hidden form variable HTML creation (for example) in the module is a design decision, the wisdom of which is in the eyes of the beholder. When I referred to "completeness" I was only referring to its functionality with respect to CGI.pm. TTYL, -Jesse- -- Jesse Erlbaum The Erlbaum Group [EMAIL PROTECTED] Phone: 212-684-6161 Fax: 212-684-6226 --------------------------------------------------------------------- Web Archive: http://www.mail-archive.com/[EMAIL PROTECTED]/ http://marc.theaimsgroup.com/?l=cgiapp&r=1&w=2 To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
