Hello, GY>mod_perl allows you to let your content handlers to focus on content - GY>all other parts of your application (authentication, session management, GY>proxying, URL rewriting tricks, etc) can programmed at the server level GY>via other parts of the request cycle.
I think the question isn't "why is Apache::Registry not sufficient to handle all functions within an HTTP request" but "why is it bad to use Apache::Request specifically for the content generation phase?" Perrin had some good practical reasons for this--caused by the generated-namespace, sub-wrapped, eval'ed nature of Apache::Registry. I totally agree with the fact that Apache::Registry can introduce many hard-to-debug-problems. I've had enough headaches debugging some of these issues myself. It's unclear to me, though, that there are unimaginably cool things you can get to in a "real" content handler that you can't get to from an Apache::Registry script--which seems to be the assertion. I mean, even from the "lowest common denominator" CGI you can get all parts of the incoming HTTP request, plus output arbitrary headers. I have found that often the Apache::Registry functionality of not having to restart servers when simple scripts change is worth the potential of bugs tickled by the Apache::Registry sub-wrap approach. I think it's a fine tool for simple content generation scripts and that it doesn't limit you at all in that aspect. Humbly, Andrew ---------------------------------------------------------------------- Andrew Ho http://www.tellme.com/ [EMAIL PROTECTED] Engineer 1-800-555-TELL Voice 650-930-9062 Tellme Networks, Inc. Fax 650-930-9101 ----------------------------------------------------------------------
