Adi wrote:
>
> Jim Winstead wrote:
> >
> > On May 05, Adi wrote:
> > > You can still use CGI.pm from within mod_perl (and you should). There is
> > > nothing better at handling data passed from a browser via HTTP POST and/or
> > > GET. If you currently use CGI.pm, I think you'll find that a lot of your
> > > current code can simply be cut-and-pasted into a mod_perl setup.
> >
> > Well, arguably Apache::Request is better at handling data passed
> > from a browser via HTTP POST and/or GET in a mod_perl environment.
> > And it has the advantage that is entirely focused on request
> > handling, and doesn't have any of the HTML generation cruft like
> > CGI.pm.
>
> Wow, I wasn't aware of Apache::Request.. thanks for letting me know.
What I would really like is a module which subclasses Apache::Request,
and has the popup_menu, scrolling_list, and checkbox group methods
available. That way I can use the smaller (faster) Apache::Request and
still have the few HTML generation methods that I need. This would be
similar to Apache::RequestNotes. One day I'll actually do it when I
convert my CGI scripts to perl handlers...
--
Drew Taylor
Vialogix Communications, Inc.
501 N. College Street
Charlotte, NC 28202
704 370 0550
http://www.vialogix.com/
