I recently gave some advice on perlmonks.org to a person who was concerned about what his migration path would be if he develops for mod_perl 1 right now. I told him he will be safe if he uses Apache::Registry, since he should be able to run his A::R scripts under ModPerl::Registry unchanged (assuming he does the workaround for chdir and uses prefork).
Another person suggested coding to the mp 1 handler API and using Apache::compat to port. I thought that would be slow and potentially bad in terms of memory used, but I'm not actually certain how these two options compare. Does anyone have any information about the comparison of ModPerl::Registry and Apache::compat in terms of performance, memory, and ease of porting? I'd like to make sure I give good advice on this topic. - Perrin
