perl-modperl mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Thomas Hilbig <>
Subject Re: [mp2] porting/co-existence questions
Date Sun, 07 Aug 2005 20:06:44 GMT
--- "Philip M. Gollucci" <> 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  APR::Request (libapreq) wasn't part of the
httpd or mp2 binary (ppm) so I hadn't noticed it

> > 	simple HTML elements 
> > 	more complex HTML elements (forms, header/body)
> shouldn't you be using templates :)
> Though to implement the template engine, I use
> for
> popup_menu() and the like.... Cleaner code, but more
> memory.

I don't have any duplication that would benefit from
templates.  popup_menu() is a good example where shines.

> I was not aware that Apache2::* or APR::* had
> methods for generating HTML.

I mean having to get into the html code instead of
using the to do it for you.  I tend not to take
advantage of the methods anyway.

> > 	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.
> > Also, the mp2 User's Guide (section 10.9.1) says
> > 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
I'm still confused why this is optional in 
Does it save some cycles by avoiding having to
sniff around for the Apache requestor?

Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 

View raw message