On Thu, 18 May 2000, brian moseley wrote:
> i suggest that instead of subclassing Apache::Request, you
> write the following set of classes:
>
> 1) html widget class
> 2) sticky forms class - use html widget class, take $r or $q
> as param
> 3) "wrapper" class - gives you the CGI.pm interface, uses
> sticky forms class, takes $r or $q as param
>
> this would give us the best of both worlds: you get a
> plug-in replacement for CGI.pm, we get a set of classes that
> aren't tightly coupled to each other. by keeping the sticky
> forms class and wrapper class separate, you allow people who
> just want sticky forms to get that, and people who want the
> whole ungodly CGI.pm interface to get that.
#1 exists in the new CGI
#2 could be integrated with the new CGI with some amount of effort (though
I doubt it would be huge). Right now the sticky forms aspect works by
having the form generating object call $self->param to set defaults. If
this were changed to call $self->{state}->param and have what's in state
be either a CGI or Apache::Request object you'd be all set.
#3 is the new CGI
I really don't think we need yet another module doing what CGI does. The
people who've worked on the new version have done a very good job of
addressing the memory and speed concerns people had about the current
monolothic version. I think its much better to extend their work than to
redo it.
-dave
/*==================
www.urth.org
We await the New Sun
==================*/
