If you only use ModPerl::Registry, you're doing fine. However, you won't be taking full advantage of mod_perl (either v2 or the equivilent for v1). A full handler gives you an awful lot of flexibility. In mod_perl2, you aren't even limited to handling just HTTP--just about any protocol implemented with TCP can be done. Maybe you won't need that extra flexibility, but you can do a lot of fun things with it.
Note that the CGI::* namespace is mostly notation. While some of it may not be applicable to a mod_perl environment, some of it is generic enough to be used under either mod_perl or mod_cgi. OTOH, some of them should be ditched in favor of mod_perl-specific modules. For instance, CGI.pm itself should probably be skipped in favor of Apache::Request, at least for parsing CGI params and setting headers.
----
send money to your kernel via the boot loader.. This and more wisdom available from Markov Hardburn.
In reply to Re: mod_perl2 design - what are the Ways To Do It ?
by hardburn
in thread mod_perl2 design - what are the Ways To Do It ?
by yosefm
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |