Colin Wetherbee wrote:
# BEGIN CODE BLOCK
my $req = Apache2::Request->new($r);
$r->content_type('text/html');
$r->print("test\n");
# END CODE BLOCK
OK, problem solved.
I didn't have mod_apreq enabled. For what it's worth, I don't recall
seeing anything about enabling mod_apreq in the
Jonathan Vanasco wrote:
As I said in my original post, I tried to use Apache2::Request, but
after creating that object, I couldn't print anything anymore.
Perhaps someone could give me a hint on how to implement it?
could you print beforehand?
'print' might not be tied to the same output.
On Jun 11, 2007, at 4:29 PM, Colin Wetherbee wrote:
That sounds good to me. I'm not looking for any particular
backward compatibility, and speed is an issue.
last i checked the speed difference is negligible. its 'more proper'
to use libapreq, and if you're doing things in term of mod_pe
Foo JH wrote:
You'd see that Apache2::Request exposes more stuff, which you can
(lazily) use. Unless you are looking for some backward compatibility to
tradditional CGI programming, why not embrace the entire modperl library?
That sounds good to me. I'm not looking for any particular backward
Foo JH 写道:
You'd see that Apache2::Request exposes more stuff, which you can
(lazily) use. Unless you are looking for some backward compatibility to
tradditional CGI programming, why not embrace the entire modperl library?
I second it.Using Apache2::Request is not harder than CGI,but much f
I've kinda moved out of CGI since I started using modperl for primarily
2 reasons: speed and functionality.
You'd see that Apache2::Request exposes more stuff, which you can
(lazily) use. Unless you are looking for some backward compatibility to
tradditional CGI programming, why not embrace th
"Perrin Harkins" <[EMAIL PROTECTED]> writes:
> On 6/10/07, Colin Wetherbee <[EMAIL PROTECTED]> wrote:
>> I know Apache2::Request is supposed to be able to grab CGI parameters;
>> is that "better" than using CGI.pm?
>
> It's faster, but CGI.pm fully supports Apache 2 and works fine. If
> speed is
On 6/10/07, Colin Wetherbee <[EMAIL PROTECTED]> wrote:
I know Apache2::Request is supposed to be able to grab CGI parameters;
is that "better" than using CGI.pm?
It's faster, but CGI.pm fully supports Apache 2 and works fine. If
speed is not an issue for you, it's fine to stick with your CGI.p
Hello!
It's been about four years since I've used mod_perl to any great extent,
and I'm afraid I'm somewhat rusty. I'm trying to create a handler that
can parse CGI parameters, but I'm unsure of the most modern way of doing
that.
I know Apache2::Request is supposed to be able to grab CGI pa
