-- George said:
> Here's my latest stab at it with comments. Added an
> abort mode and changed some identifiers, including
> capitalizing run modes to avoid confusion with
> built-in Perl funcs. Still my main CGI::Application
> question is, does it save any overhead to pass $cgi as
> a $self->param? Could be an issue, because though I'm
> starting on a Windows based intranet and am using
> ActiveState's PerlISAPI, this could be ported to a
> virtually hosted Linux machine where it might have to
> run as CGI rather than under mod_perl.
>
> Thanks!!
Hello George,
To address your question about the $cgi object, it shouldn't really make a
difference to stick it in as a $self->param(). But you do not need to do that
at all. In each of your run modes you can access the $cgi object by using the
same two lines of code that you have in your setup() subroutine:
my $self = shift;
my $cgi = $self->query();
Based on the setup code you provided, you would have to change this in your
run modes to look like this:
my $self = shift;
my $cgi = $self->param('cgi');
But that's just doing the same thing. Except in your case, you're just
typing more, and adding a line of code in your setup() that doesn't need to be
there. So, no it doesn't save any overhead. If anything, it adds to it (but
we're talking miliseconds here).
-spencer christensen
[EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
