mod_perl 2 migration problems

Hi, I'm trying to migrate some existing mod_perl 1 code to mod_perl 2. The original code uses many calls like:

my $value = $r->args->{'foo'};
$r->args->{'foo'} = "bar";
[download]

to get and set request parameters. I couldn't seem to find an equivalent in mod_perl 2, Apache2::Request allows retrieving parameters by its param() method, but no way to set the parameters to be processed further down the chain, thanks.

Comment on mod_perl 2 migration problems Download Code
Re: mod_perl 2 migration problems by perrin (Chancellor) on Sep 14, 2006 at 16:35 UTC
What you're doing here (changing the actual input) is kind of a bad idea. It would be better to use some kind of internal data structure for passing around your processed parameters, maybe storing them in a hash in $r->pnotes().	[reply]
Re^2: mod_perl 2 migration problems by johnnywang (Priest) on Sep 14, 2006 at 16:43 UTC
well, yes, but I'm working with someone else's code, and can't really re-write everything at the moment.	[reply]
Re^3: mod_perl 2 migration problems by perrin (Chancellor) on Sep 14, 2006 at 18:26 UTC
Well, you have to change code that uses $r->args to parse the query string because that doesn't work anymore. See the porting doc for more info. You can set the complete query string with $r->args(), which might allow later code to see your parameter changes, or you might be able to use Apache2::Request and modify the params using the APR::Table API on the object it returns when you call it like this: `my $table = $req->param;` [download] I'm not sure those changes are visible to anyone else though.	[reply] [d/l]
Re^4: mod_perl 2 migration problems by johnnywang (Priest) on Sep 14, 2006 at 19:56 UTC


Think about Loose Coupling
	PerlMonks

mod_perl 2 migration problems

The best material for plates (tableware) is: