Philip M. Gollucci wrote:
Stas Bekman wrote:
print vs. $r->print
This is drastically faster.. especially if you use
one print
per request at the end and/or pass a reference to
the scalar string.
Actually this is no longer true. in mp2 you can't pass a reference to
a scalar.
Still
Stas Bekman wrote:
print vs. $r->print
This is drastically faster.. especially if you use
one print
per request at the end and/or pass a reference to
the scalar string.
Actually this is no longer true. in mp2 you can't pass a reference to a
scalar.
Still $r->print is faster :)
I t
print vs. $r->print
This is drastically faster.. especially if you use
one print
per request at the end and/or pass a reference to
the scalar string.
Actually this is no longer true. in mp2 you can't pass a reference to a
scalar.
Still $r->print is faster :)
Also, the mp2 User's
Thomas Hilbig wrote:
Also, the mp2 User's Guide (section 10.9.1) says
CGI.pm now takes $r as an argument to its new()
function. What benefit is this? Is it required?
For the most part its optional.
You may need to look at PerlGlobalRequest
http://perl.apache.org/docs/2.0/user/config/confi
--- "Philip M. Gollucci" <[EMAIL PROTECTED]> wrote:
> > fetching/setting cookies
> > fetching parameters (GET arguments or POST)
> use APR::Request::*
> Its faster as its in XS glue code.
That does look like it will do it just as simply as
CGI.pm. APR::Request (libapreq) wasn't part of th
fetching/setting cookies
fetching parameters (GET arguments or POST)
use APR::Request::*
Its faster as its in XS glue code.
simple HTML elements
more complex HTML elements (forms, header/body)
shouldn't you be using templates :)
Though to implement the template engine, I use
I have many CGI scripts running under mp2 using
ModPerl::Registry, that I want to re-architect to use
more Apache API's (for speed) and handlers (i.e.
authentication, logging).
I have been getting up to speed on the mp2 docs these
past couple of weeks.I haven't really seen any
good recommenda
