more useful options | |
PerlMonks |
comment on |
( [id://3333]=superdoc: print w/replies, xml ) | Need Help?? |
I am not a mod_perl guru by any means, but I have recently deployed a relatively large app from the ground up using MP2.
There are (at least!) two different ways to handle a request using mod_perl. The first is using mod_perl handlers and the other is using CGI scripts. I use ModPerl::Registry and it works really well. I have them running large CGI::Application classes and it's great! Speed boosts are great. MP handlers are Perl classes that have access to the Apache internals to do their business. They are very very very fast. They also have a very different interface, which also isn't fully finished. (There recently was a major API change in the latest mod_perl 1.99_x release.) I, personally, would wait until there is a mod_perl 2.0_x release before writing handlers against it, but that's just me. Now, from what I've read, it seems possible to have CGI::Application classes be mod_perl handlers, but I haven't seen anyone else do it, so I don't know if I'm stunningly brilliant or just missing something. ------
Then there are Damian modules.... *sigh* ... that's not about being less-lazy -- that's about being on some really good drugs -- you know, there is no spoon. - flyingmoose I shouldn't have to say this, but any code, unless otherwise stated, is untested In reply to Re: mod_perl2 design - what are the Ways To Do It ?
by dragonchild
|
|