Henri Icarus has asked for the wisdom of the Perl Monks concerning the following question:

I'm diving in to convert my CGI based web app to mod_perl and I've read the porting guide over at perl.apache.org but I'm confused about how inter-operable CGI.pm is with Apache::Request. Specifically, it doesn't look like such methods as "delete" and "delete_all" are available in Apache::Request.

Any advice from those who have converted over and how they've handled this issue?

Thanks!

-I went outside... and then I came back in!!!!

Replies are listed 'Best First'.
Re: CGI.pm vs Apache::Request
by doink123 (Sexton) on Jun 22, 2005 at 07:16 UTC
    CGI.pm works perfect with mod_perl. You don't need to move to Apache::Request.
[reply]
      I understand that CGI.pm works, I'm trying to get the speed and memory use gains that come with Apache::Request. Thus the need to upgrade.

      -I went outside... and then I came back in!!!!

[reply]
Re: CGI.pm vs Apache::Request
by Ctrl-z (Friar) on Jun 23, 2005 at 13:02 UTC

    Im new to Apache::Request myself, so take this with a pinch of salt...

    Have you looked at Apache::Table? It provides similar functionality: 

            my $q = Apache::Request->new(shift);
        my $table = $q->parms;
        $table->clear;

    [download]

    You could create an Apache::Request subclass with CGI.pm's full API, eg

    package CGIRequest;
use base Apache::Request;

sub new
{
    my $class = shift;
    return bless Apache::Request->new(@_), $class;
}

sub delete_all
{
    my $self = shift;
    $self->parms()->clear();
}

# ...etc

1;

    [download]

    A quick test of the above code appears to be ok...

    Hope that helps




    time was, I could move my arms like a bird and...
[reply]
[d/l]
[select]

Back to Seekers of Perl Wisdom