it would be nice to have a wrapper around Apache::Request that supplies the "missing" methods. That wrapper would function like a normal CGI.pm object for all the CGI::App cares.
I like this idea. It seems like there would be some edge cases, though.
If you set something with 'param' with one object, you would want it to
appear in the other ones. It seems that to be truly transparent,
you have to sync the params back and forth between the objects each time
you switch from one to the other. Could be a real pain.
Well, by wrapping I mean, the param() will just call the underlying method of Apache::Request.
It will not keep any state itself.
It would work as a drop-in replacement, just like CGI::Simple.
CGI::Simple is only a replacement for /most/ methods. It has several documented differents. I believe it handles file uploads a little diferently, not to mention missing of all the HTML generation methods. ( I still use popup_menu() ).
Sure.
Not doing all the HTML stuff (and having to load it) is I think the main motivation for CGI::Simple.
But CGI::Simple is compatible enough to work with CGI::App (and other modules if they are coded liberally, unlike CGI::Session as recently discussed).
It would be nice to have something similar for Apache::Request.
Thilo
--------------------------------------------------------------------- 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]
